vouchington-tooling 2.0.2 → 3.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +2 -2
- package/scripts/__pycache__/run_bounded_process.cpython-314.pyc +0 -0
- package/skills/manifest.json +15 -202
- package/skills/organize-github-issues/SKILL.md +20 -3
- package/skills/pr-description/SKILL.md +9 -65
- package/skills/retrospective/SKILL.md +16 -1
- package/skills/retrospective-distill/SKILL.md +1 -1
- package/skills/retrospective-distill/references/issue-body.md +6 -1
- package/skills/review-github-issue-taxonomy/SKILL.md +3 -4
- package/skills/triage-loop/SKILL.md +111 -34
- package/skills/triage-prs/SKILL.md +26 -28
- package/skills/triage-prs/references/feedback.md +14 -2
- package/skills/triage-prs/references/rubric.md +4 -4
- package/skills/triage-sweep/SKILL.md +26 -23
- package/skills/agent-workflow/SKILL.md +0 -72
- package/skills/agent-workflow/references/evidence-sweep.md +0 -12
- package/skills/agent-workflow/references/four-refs.md +0 -74
- package/skills/agent-workflow/references/implementation-and-review.md +0 -4
- package/skills/agent-workflow/references/implementation.md +0 -20
- package/skills/agent-workflow/references/review-response.md +0 -49
- package/skills/agent-workflow/references/review.md +0 -10
- package/skills/backend-vitest-test-authoring/SKILL.md +0 -22
- package/skills/backend-vitest-test-authoring/references/integration-boundaries.md +0 -10
- package/skills/bounded-iteration/SKILL.md +0 -92
- package/skills/bounded-iteration/references/sweep-patterns.md +0 -719
- package/skills/dependabot/SKILL.md +0 -117
- package/skills/dotnet-test-authoring/SKILL.md +0 -24
- package/skills/git-commit-checklist/SKILL.md +0 -29
- package/skills/github-actions-authoring/SKILL.md +0 -63
- package/skills/github-actions-checklist/SKILL.md +0 -118
- package/skills/github-issue/SKILL.md +0 -121
- package/skills/glide-mq/SKILL.md +0 -52
- package/skills/glide-mq/references/lease-patterns.md +0 -44
- package/skills/nextjs-vitest-test-authoring/SKILL.md +0 -21
- package/skills/nextjs-vitest-test-authoring/references/framework-boundaries.md +0 -9
- package/skills/npm-publishing/SKILL.md +0 -72
- package/skills/package-json-checklist/SKILL.md +0 -31
- package/skills/planning/SKILL.md +0 -37
- package/skills/planning/references/impact-discovery.md +0 -11
- package/skills/playwright-authoring/SKILL.md +0 -23
- package/skills/playwright-authoring/references/browser-reliability.md +0 -9
- package/skills/postgres-node-performance-tuning/SKILL.md +0 -35
- package/skills/postgres-node-performance-tuning/references/performance-patterns.md +0 -175
- package/skills/postgres-node-performance-tuning/references/reading-plans.md +0 -111
- package/skills/postgres-partitioning-uuid-v7/SKILL.md +0 -35
- package/skills/postgres-partitioning-uuid-v7/references/partition-lifecycle.md +0 -53
- package/skills/postgres-schema-design/SKILL.md +0 -31
- package/skills/postgres-schema-design/references/naming.md +0 -34
- package/skills/postgres-schema-design/references/relations.md +0 -66
- package/skills/postgres-schema-design/references/table-shapes.md +0 -78
- package/skills/pr-description/references/examples.md +0 -189
- package/skills/review-ci-logs/SKILL.md +0 -44
- package/skills/revisit-followups/SKILL.md +0 -47
- package/skills/stacked-prs/SKILL.md +0 -98
- package/skills/stacked-prs/references/drain.md +0 -177
- package/skills/stacked-prs/references/gh-stack.md +0 -147
- package/skills/static-analysis-checklist/SKILL.md +0 -32
- package/skills/storybook-authoring/SKILL.md +0 -22
- package/skills/storybook-authoring/references/component-coverage.md +0 -9
- package/skills/swift-test-authoring/SKILL.md +0 -23
- package/skills/swift-test-authoring/references/network-test-doubles.md +0 -9
- package/skills/test-authoring/SKILL.md +0 -27
- package/skills/test-authoring/references/core-practice.md +0 -16
- package/skills/test-authoring/references/dependency-boundaries.md +0 -38
- package/skills/test-authoring/references/tautological-tests.md +0 -47
- package/skills/triage-loop/references/shepherd.md +0 -64
- package/skills/vitest-test-authoring/SKILL.md +0 -22
- package/skills/vitest-test-authoring/references/mock-boundaries.md +0 -9
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "vouchington-tooling",
|
|
3
|
-
"version": "
|
|
3
|
+
"version": "3.0.1",
|
|
4
4
|
"description": "Vouchington CLI and extractable tooling libraries.",
|
|
5
5
|
"homepage": "https://github.com/vouchington/vouchington-tooling/tree/main/packages/vouchington-tooling#readme",
|
|
6
6
|
"bugs": {
|
|
@@ -525,7 +525,7 @@
|
|
|
525
525
|
"@vouchington/worker-runtime": "0.3.1",
|
|
526
526
|
"glide-mq": "^0.20.0",
|
|
527
527
|
"next": "16.4.5",
|
|
528
|
-
"no-mistakes": "0.109.
|
|
528
|
+
"no-mistakes": "0.109.29",
|
|
529
529
|
"pg": "8.23.1",
|
|
530
530
|
"react": "19.3.1",
|
|
531
531
|
"react-dom": "19.3.1",
|
|
Binary file
|
package/skills/manifest.json
CHANGED
|
@@ -1,254 +1,67 @@
|
|
|
1
1
|
{
|
|
2
2
|
"version": 1,
|
|
3
3
|
"skills": [
|
|
4
|
-
{
|
|
5
|
-
"name": "agent-workflow",
|
|
6
|
-
"plugin": "vouchington-workflow",
|
|
7
|
-
"pluginVersion": "0.20.1",
|
|
8
|
-
"path": "agent-workflow/SKILL.md",
|
|
9
|
-
"prerequisites": [
|
|
10
|
-
"blackboard",
|
|
11
|
-
"github-issue",
|
|
12
|
-
"pr-description",
|
|
13
|
-
"retrospective",
|
|
14
|
-
"review-ci-logs"
|
|
15
|
-
]
|
|
16
|
-
},
|
|
17
|
-
{
|
|
18
|
-
"name": "backend-vitest-test-authoring",
|
|
19
|
-
"plugin": "vouchington-testing",
|
|
20
|
-
"pluginVersion": "0.2.0",
|
|
21
|
-
"path": "backend-vitest-test-authoring/SKILL.md",
|
|
22
|
-
"prerequisites": ["vitest-test-authoring"]
|
|
23
|
-
},
|
|
24
4
|
{
|
|
25
5
|
"name": "blackboard",
|
|
26
6
|
"plugin": "vouchington-workflow",
|
|
27
|
-
"pluginVersion": "0.
|
|
7
|
+
"pluginVersion": "0.23.2",
|
|
28
8
|
"path": "blackboard/SKILL.md"
|
|
29
9
|
},
|
|
30
|
-
{
|
|
31
|
-
"name": "bounded-iteration",
|
|
32
|
-
"plugin": "vouchington-database",
|
|
33
|
-
"pluginVersion": "0.11.0",
|
|
34
|
-
"path": "bounded-iteration/SKILL.md"
|
|
35
|
-
},
|
|
36
|
-
{
|
|
37
|
-
"name": "dependabot",
|
|
38
|
-
"plugin": "vouchington-workflow",
|
|
39
|
-
"pluginVersion": "0.20.1",
|
|
40
|
-
"path": "dependabot/SKILL.md",
|
|
41
|
-
"prerequisites": ["github-actions-checklist"]
|
|
42
|
-
},
|
|
43
|
-
{
|
|
44
|
-
"name": "dotnet-test-authoring",
|
|
45
|
-
"plugin": "vouchington-testing",
|
|
46
|
-
"pluginVersion": "0.2.0",
|
|
47
|
-
"path": "dotnet-test-authoring/SKILL.md",
|
|
48
|
-
"prerequisites": ["test-authoring"]
|
|
49
|
-
},
|
|
50
|
-
{
|
|
51
|
-
"name": "git-commit-checklist",
|
|
52
|
-
"plugin": "vouchington-workflow",
|
|
53
|
-
"pluginVersion": "0.20.1",
|
|
54
|
-
"path": "git-commit-checklist/SKILL.md"
|
|
55
|
-
},
|
|
56
|
-
{
|
|
57
|
-
"name": "github-actions-authoring",
|
|
58
|
-
"plugin": "vouchington-workflow",
|
|
59
|
-
"pluginVersion": "0.20.1",
|
|
60
|
-
"path": "github-actions-authoring/SKILL.md",
|
|
61
|
-
"prerequisites": ["github-actions-checklist"]
|
|
62
|
-
},
|
|
63
|
-
{
|
|
64
|
-
"name": "github-actions-checklist",
|
|
65
|
-
"plugin": "vouchington-workflow",
|
|
66
|
-
"pluginVersion": "0.20.1",
|
|
67
|
-
"path": "github-actions-checklist/SKILL.md"
|
|
68
|
-
},
|
|
69
|
-
{
|
|
70
|
-
"name": "github-issue",
|
|
71
|
-
"plugin": "vouchington-workflow",
|
|
72
|
-
"pluginVersion": "0.20.1",
|
|
73
|
-
"path": "github-issue/SKILL.md"
|
|
74
|
-
},
|
|
75
|
-
{
|
|
76
|
-
"name": "glide-mq",
|
|
77
|
-
"plugin": "vouchington-database",
|
|
78
|
-
"pluginVersion": "0.11.0",
|
|
79
|
-
"path": "glide-mq/SKILL.md"
|
|
80
|
-
},
|
|
81
|
-
{
|
|
82
|
-
"name": "nextjs-vitest-test-authoring",
|
|
83
|
-
"plugin": "vouchington-testing",
|
|
84
|
-
"pluginVersion": "0.2.0",
|
|
85
|
-
"path": "nextjs-vitest-test-authoring/SKILL.md",
|
|
86
|
-
"prerequisites": ["vitest-test-authoring"]
|
|
87
|
-
},
|
|
88
|
-
{
|
|
89
|
-
"name": "npm-publishing",
|
|
90
|
-
"plugin": "vouchington-workflow",
|
|
91
|
-
"pluginVersion": "0.20.1",
|
|
92
|
-
"path": "npm-publishing/SKILL.md"
|
|
93
|
-
},
|
|
94
10
|
{
|
|
95
11
|
"name": "organize-github-issues",
|
|
96
12
|
"plugin": "vouchington-workflow",
|
|
97
|
-
"pluginVersion": "0.
|
|
98
|
-
"path": "organize-github-issues/SKILL.md"
|
|
99
|
-
"prerequisites": ["github-issue"]
|
|
100
|
-
},
|
|
101
|
-
{
|
|
102
|
-
"name": "package-json-checklist",
|
|
103
|
-
"plugin": "vouchington-workflow",
|
|
104
|
-
"pluginVersion": "0.20.1",
|
|
105
|
-
"path": "package-json-checklist/SKILL.md"
|
|
106
|
-
},
|
|
107
|
-
{
|
|
108
|
-
"name": "planning",
|
|
109
|
-
"plugin": "vouchington-workflow",
|
|
110
|
-
"pluginVersion": "0.20.1",
|
|
111
|
-
"path": "planning/SKILL.md",
|
|
112
|
-
"prerequisites": ["github-issue"]
|
|
113
|
-
},
|
|
114
|
-
{
|
|
115
|
-
"name": "playwright-authoring",
|
|
116
|
-
"plugin": "vouchington-testing",
|
|
117
|
-
"pluginVersion": "0.2.0",
|
|
118
|
-
"path": "playwright-authoring/SKILL.md",
|
|
119
|
-
"prerequisites": ["test-authoring"]
|
|
120
|
-
},
|
|
121
|
-
{
|
|
122
|
-
"name": "postgres-node-performance-tuning",
|
|
123
|
-
"plugin": "vouchington-database",
|
|
124
|
-
"pluginVersion": "0.11.0",
|
|
125
|
-
"path": "postgres-node-performance-tuning/SKILL.md"
|
|
126
|
-
},
|
|
127
|
-
{
|
|
128
|
-
"name": "postgres-partitioning-uuid-v7",
|
|
129
|
-
"plugin": "vouchington-database",
|
|
130
|
-
"pluginVersion": "0.11.0",
|
|
131
|
-
"path": "postgres-partitioning-uuid-v7/SKILL.md"
|
|
132
|
-
},
|
|
133
|
-
{
|
|
134
|
-
"name": "postgres-schema-design",
|
|
135
|
-
"plugin": "vouchington-database",
|
|
136
|
-
"pluginVersion": "0.11.0",
|
|
137
|
-
"path": "postgres-schema-design/SKILL.md"
|
|
13
|
+
"pluginVersion": "0.23.2",
|
|
14
|
+
"path": "organize-github-issues/SKILL.md"
|
|
138
15
|
},
|
|
139
16
|
{
|
|
140
17
|
"name": "pr-description",
|
|
141
18
|
"plugin": "vouchington-workflow",
|
|
142
|
-
"pluginVersion": "0.
|
|
19
|
+
"pluginVersion": "0.23.2",
|
|
143
20
|
"path": "pr-description/SKILL.md"
|
|
144
21
|
},
|
|
145
22
|
{
|
|
146
23
|
"name": "retrospective",
|
|
147
24
|
"plugin": "vouchington-workflow",
|
|
148
|
-
"pluginVersion": "0.
|
|
25
|
+
"pluginVersion": "0.23.2",
|
|
149
26
|
"path": "retrospective/SKILL.md"
|
|
150
27
|
},
|
|
151
28
|
{
|
|
152
29
|
"name": "retrospective-distill",
|
|
153
30
|
"plugin": "vouchington-workflow",
|
|
154
|
-
"pluginVersion": "0.
|
|
155
|
-
"path": "retrospective-distill/SKILL.md"
|
|
156
|
-
"prerequisites": ["github-issue"]
|
|
157
|
-
},
|
|
158
|
-
{
|
|
159
|
-
"name": "review-ci-logs",
|
|
160
|
-
"plugin": "vouchington-workflow",
|
|
161
|
-
"pluginVersion": "0.20.1",
|
|
162
|
-
"path": "review-ci-logs/SKILL.md",
|
|
163
|
-
"prerequisites": ["github-actions-checklist", "pr-description"]
|
|
31
|
+
"pluginVersion": "0.23.2",
|
|
32
|
+
"path": "retrospective-distill/SKILL.md"
|
|
164
33
|
},
|
|
165
34
|
{
|
|
166
35
|
"name": "review-github-issue-taxonomy",
|
|
167
36
|
"plugin": "vouchington-workflow",
|
|
168
|
-
"pluginVersion": "0.
|
|
37
|
+
"pluginVersion": "0.23.2",
|
|
169
38
|
"path": "review-github-issue-taxonomy/SKILL.md",
|
|
170
|
-
"prerequisites": ["github-
|
|
171
|
-
},
|
|
172
|
-
{
|
|
173
|
-
"name": "revisit-followups",
|
|
174
|
-
"plugin": "vouchington-workflow",
|
|
175
|
-
"pluginVersion": "0.20.1",
|
|
176
|
-
"path": "revisit-followups/SKILL.md",
|
|
177
|
-
"prerequisites": ["github-issue"]
|
|
178
|
-
},
|
|
179
|
-
{
|
|
180
|
-
"name": "stacked-prs",
|
|
181
|
-
"plugin": "vouchington-workflow",
|
|
182
|
-
"pluginVersion": "0.20.1",
|
|
183
|
-
"path": "stacked-prs/SKILL.md"
|
|
184
|
-
},
|
|
185
|
-
{
|
|
186
|
-
"name": "static-analysis-checklist",
|
|
187
|
-
"plugin": "vouchington-workflow",
|
|
188
|
-
"pluginVersion": "0.20.1",
|
|
189
|
-
"path": "static-analysis-checklist/SKILL.md",
|
|
190
|
-
"prerequisites": ["github-actions-checklist"]
|
|
191
|
-
},
|
|
192
|
-
{
|
|
193
|
-
"name": "storybook-authoring",
|
|
194
|
-
"plugin": "vouchington-testing",
|
|
195
|
-
"pluginVersion": "0.2.0",
|
|
196
|
-
"path": "storybook-authoring/SKILL.md",
|
|
197
|
-
"prerequisites": ["test-authoring"]
|
|
198
|
-
},
|
|
199
|
-
{
|
|
200
|
-
"name": "swift-test-authoring",
|
|
201
|
-
"plugin": "vouchington-testing",
|
|
202
|
-
"pluginVersion": "0.2.0",
|
|
203
|
-
"path": "swift-test-authoring/SKILL.md",
|
|
204
|
-
"prerequisites": ["test-authoring"]
|
|
205
|
-
},
|
|
206
|
-
{
|
|
207
|
-
"name": "test-authoring",
|
|
208
|
-
"plugin": "vouchington-testing",
|
|
209
|
-
"pluginVersion": "0.2.0",
|
|
210
|
-
"path": "test-authoring/SKILL.md"
|
|
39
|
+
"prerequisites": ["organize-github-issues"]
|
|
211
40
|
},
|
|
212
41
|
{
|
|
213
42
|
"name": "triage-loop",
|
|
214
43
|
"plugin": "vouchington-workflow",
|
|
215
|
-
"pluginVersion": "0.
|
|
216
|
-
"path": "triage-loop/SKILL.md"
|
|
217
|
-
"prerequisites": ["github-issue", "stacked-prs"]
|
|
44
|
+
"pluginVersion": "0.23.2",
|
|
45
|
+
"path": "triage-loop/SKILL.md"
|
|
218
46
|
},
|
|
219
47
|
{
|
|
220
48
|
"name": "triage-prs",
|
|
221
49
|
"plugin": "vouchington-workflow",
|
|
222
|
-
"pluginVersion": "0.
|
|
50
|
+
"pluginVersion": "0.23.2",
|
|
223
51
|
"path": "triage-prs/SKILL.md",
|
|
224
|
-
"prerequisites": [
|
|
225
|
-
"pr-description",
|
|
226
|
-
"retrospective",
|
|
227
|
-
"review-ci-logs",
|
|
228
|
-
"github-issue",
|
|
229
|
-
"stacked-prs"
|
|
230
|
-
]
|
|
52
|
+
"prerequisites": ["pr-description", "retrospective"]
|
|
231
53
|
},
|
|
232
54
|
{
|
|
233
55
|
"name": "triage-sweep",
|
|
234
56
|
"plugin": "vouchington-workflow",
|
|
235
|
-
"pluginVersion": "0.
|
|
57
|
+
"pluginVersion": "0.23.2",
|
|
236
58
|
"path": "triage-sweep/SKILL.md",
|
|
237
59
|
"prerequisites": [
|
|
238
60
|
"triage-loop",
|
|
239
|
-
"review-ci-logs",
|
|
240
61
|
"triage-prs",
|
|
241
62
|
"organize-github-issues",
|
|
242
|
-
"retrospective-distill"
|
|
243
|
-
"github-issue"
|
|
63
|
+
"retrospective-distill"
|
|
244
64
|
]
|
|
245
|
-
},
|
|
246
|
-
{
|
|
247
|
-
"name": "vitest-test-authoring",
|
|
248
|
-
"plugin": "vouchington-testing",
|
|
249
|
-
"pluginVersion": "0.2.0",
|
|
250
|
-
"path": "vitest-test-authoring/SKILL.md",
|
|
251
|
-
"prerequisites": ["test-authoring"]
|
|
252
65
|
}
|
|
253
66
|
]
|
|
254
67
|
}
|
|
@@ -14,13 +14,13 @@ local `AGENTS.md`, and live taxonomy guidance before acting.
|
|
|
14
14
|
|
|
15
15
|
1. Confirm repository identity. Fetch live labels, milestone descriptions, open project
|
|
16
16
|
descriptions, and the in-scope issue or pull-request evidence. Before a mutation, apply the
|
|
17
|
-
|
|
17
|
+
"Authority to write" section of the `github-issue` skill (`skills` plugin). Pull-request metadata
|
|
18
18
|
does not require issues to be enabled.
|
|
19
19
|
2. Classify from the permitted metadata and discussion. Do not guess from the implementation. Keep
|
|
20
20
|
automation, ownership, and provenance labels unless local policy explicitly allows a change.
|
|
21
21
|
3. Apply only existing labels, milestones, and projects without requesting separate label approval.
|
|
22
|
-
Follow [
|
|
23
|
-
sub-issues, and a status that closes the issue. Do not create taxonomy, close work, rewrite
|
|
22
|
+
Follow [Projects and milestones](#projects-and-milestones) for single-project membership,
|
|
23
|
+
auto-added sub-issues, and a status that closes the issue. Do not create taxonomy, close work, rewrite
|
|
24
24
|
bodies, or change titles unless the caller separately authorizes that scope.
|
|
25
25
|
4. In review mode, report the exact proposed metadata changes and do not mutate. In apply mode,
|
|
26
26
|
make only necessary, idempotent updates.
|
|
@@ -29,5 +29,22 @@ local `AGENTS.md`, and live taxonomy guidance before acting.
|
|
|
29
29
|
project's automation pulled in, such as a parent issue's sub-issues. Report changed, unchanged,
|
|
30
30
|
and ambiguous items separately.
|
|
31
31
|
|
|
32
|
+
## Projects and milestones
|
|
33
|
+
|
|
34
|
+
- Use an existing open project for strategic, initiative-level tracking and a milestone for
|
|
35
|
+
repo-local release or sequencing. Choose by the initiative, not by how many repositories it
|
|
36
|
+
touches. An initiative can have both. An issue belongs to at most one project, and not every
|
|
37
|
+
issue needs one.
|
|
38
|
+
- Before adding a project item, check that item and any item the project's automation could pull
|
|
39
|
+
in with it, such as a parent issue's sub-issues. If any already belongs to a different project,
|
|
40
|
+
skip the add and report the conflict. After the add, re-read the project.
|
|
41
|
+
- Missing project scope or permission skips the project step only. Report the gap; the issue and
|
|
42
|
+
its other metadata still proceed.
|
|
43
|
+
- Do not set a project status that closes the issue unless closing is separately authorized.
|
|
44
|
+
GitHub's Auto-close issue workflow closes the issue when status becomes Done.
|
|
45
|
+
- A plan issue takes its source's milestone. When the source already has a project, refetch
|
|
46
|
+
memberships and apply that project only when exactly one accessible open membership exists;
|
|
47
|
+
otherwise skip the project and report the conflict.
|
|
48
|
+
|
|
32
49
|
Consumer wrapper owns: priorities, labels, milestones, projects, clarification policy, default
|
|
33
50
|
scope, and permissions.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: pr-description
|
|
3
|
-
description:
|
|
3
|
+
description: Create, update, and validate pull request descriptions through the vouchington `pr_create`, `pr_update`, and `pr_validate` MCP tools.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Pull-request description
|
|
@@ -9,77 +9,21 @@ Read applicable `AGENTS.md` and their declared adapter alias, otherwise
|
|
|
9
9
|
`.agents/skills/pr-description/SKILL.md` from the repository root if present.
|
|
10
10
|
Local policy overrides these defaults; do not reload an already-read adapter or canonical skill.
|
|
11
11
|
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
Write for a reviewer who has not seen the conversation or the code. Use plain language and short
|
|
16
|
-
bullets, not dense paragraphs of internal terms. Its visible core explains:
|
|
17
|
-
|
|
18
|
-
- **Summary:** open with one or two sentences on the outcome in plain terms. Then give a
|
|
19
|
-
**Why:** that names the concrete problem or risk, such as who could do what before this change.
|
|
20
|
-
For a fix, give the root cause as well as the symptom.
|
|
21
|
-
- **Before/after table:** for any behavior change, add a visible table whose rows are concrete
|
|
22
|
-
scenarios, such as requests, configurations, environments, inputs, or user actions. Its columns
|
|
23
|
-
are the situation, the behavior before, and the behavior after. Include the unchanged cases a
|
|
24
|
-
reviewer would worry about, and the error or status each failure case returns.
|
|
25
|
-
- **Diagram:** when a request or event crosses components, add a Mermaid `sequenceDiagram` of the
|
|
26
|
-
new flow. Use a `flowchart` for decision logic or changed architecture. Keep the main diagram
|
|
27
|
-
visible.
|
|
28
|
-
- **Impact:** one bullet per affected audience, such as end users, staff, native or API clients,
|
|
29
|
-
operators, or contributors, saying what each one sees. Say when the change is active: what
|
|
30
|
-
enables it, such as a plan tier, feature flag, environment, configuration value, or rollout
|
|
31
|
-
step, and whether current deployments already satisfy it. Name the configuration it reads and
|
|
32
|
-
its defaults. Keep risks, limitations, and dependent follow-ups visible.
|
|
33
|
-
|
|
34
|
-
Put implementation detail under **Details**, grouped by subsystem with short headings. Name the
|
|
35
|
-
files and functions that carry each part, so a reviewer can find them. Leave CI history, rebase
|
|
36
|
-
narrative, and local test lists out of the body; the Shepherd Journal and evidence record hold
|
|
37
|
-
them.
|
|
38
|
-
|
|
39
|
-
Add detail only where the change warrants it:
|
|
40
|
-
|
|
41
|
-
- For cost changes, state the direction and scope. Label figures as measured or estimated, name the
|
|
42
|
-
workload and assumptions, and link evidence. Say unmeasured when no defensible figure exists;
|
|
43
|
-
do not invent savings or claim a neutral cost without evidence. Follow the consumer's privacy
|
|
44
|
-
policy before reporting actual spending, and use approved aggregated or redacted evidence.
|
|
45
|
-
- For database changes, inventory added, removed, and changed tables, columns, constraints, and
|
|
46
|
-
indexes. Explain the relationships and conformance to the consumer's schema rules, including
|
|
47
|
-
producer/consumer changes and any justified exceptions. Link the policy and concrete evidence.
|
|
48
|
-
- For API, workflow, or independently deployed changes, explain the affected contract, lifecycle,
|
|
49
|
-
or operational safety. Follow the consumer's compatibility and deployment policy.
|
|
50
|
-
- A one-line fix with no new scenarios needs only prose. Skip the table and diagram there.
|
|
51
|
-
|
|
52
|
-
Put long inventories, secondary diagrams, calculations, and failure evidence in collapsed
|
|
53
|
-
`<details>` sections. Keep the summary, the main before/after table, the main diagram, and
|
|
54
|
-
material risks outside them. Keep the
|
|
55
|
-
consumer's required visible core headings outside disclosure containers. Put opening/closing tags
|
|
56
|
-
on separate lines, with a blank line after `</summary>` and before `</details>` so Markdown renders.
|
|
57
|
-
Read [description examples](references/examples.md) when choosing a comparison, diagram, or failure
|
|
58
|
-
record.
|
|
59
|
-
|
|
60
|
-
Do not fill the description with routine local successful-test lists. This is a reporting rule,
|
|
61
|
-
not permission to skip checks: execute required validation and retain its revision, exact scope,
|
|
62
|
-
result, and any omission reason in the work's evidence record.
|
|
63
|
-
|
|
64
|
-
Include **Harness gaps** only after CI diagnosis establishes an omitted local verification or a
|
|
65
|
-
proven local/CI mismatch. Link the first failing run/job and its exact head revision, compare the actual local and
|
|
66
|
-
CI scope, explain the omission or difference, and record the durable correction or authorized
|
|
67
|
-
linked follow-up. Distinguish an omitted check from one that passed locally. Unknown coverage is
|
|
68
|
-
not evidence of a miss; classify genuine CI-only or external infrastructure failures separately.
|
|
69
|
-
Retain confirmed gap records after CI turns green. Diagnose the failure through the repository's
|
|
70
|
-
CI investigation workflow; a failed status alone does not establish a gap.
|
|
12
|
+
The rules for what a description says (the problem, the change, the impact, before/after evidence,
|
|
13
|
+
and how much detail to add) live in the `pr-description` skill from the `jonathanong/skills`
|
|
14
|
+
plugin. This skill covers only what depends on the vouchington MCP tools.
|
|
71
15
|
|
|
72
16
|
Create, update, and validate pull requests through the `pr_create`, `pr_update`, and `pr_validate`
|
|
73
17
|
MCP tools with structured input, not by hand-writing a body: pass `title`, `summary`, `impact`,
|
|
74
18
|
`relatedIssues` (`closes` or `refs`, each with a reason), `details` (Markdown paragraphs or
|
|
75
19
|
bullets), `base`, `agent`, optional `model`, `mode`, and `workspaceSetup`. The server renders the
|
|
76
20
|
required headings and provenance lines, runs the repository's policy validation, and blocks on its
|
|
77
|
-
errors, so put the guidance
|
|
78
|
-
to preview the rendered body.
|
|
21
|
+
errors, so put the description guidance into `summary`, `impact`, and `details`. Run `pr_validate`
|
|
22
|
+
first to preview the rendered body.
|
|
79
23
|
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
|
|
24
|
+
The Shepherd Journal section belongs to the review automation. `pr_update` preserves the live
|
|
25
|
+
Shepherd Journal; never copy, rewrite, or hand-edit it. Leave CI history, rebase narrative, and
|
|
26
|
+
local test lists out of the body; the Shepherd Journal and evidence record hold them.
|
|
83
27
|
|
|
84
28
|
Consumer wrapper owns: required headings, source-issue rule, merge policy, repository command, and
|
|
85
29
|
hosted review system.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: retrospective
|
|
3
|
-
description: Summarize completed work from verified facts and the session journal.
|
|
3
|
+
description: Summarize completed work from verified facts and the session journal, including when handing a PR to a human.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Retrospective
|
|
@@ -54,6 +54,21 @@ answer is `unknown — no journal`, never a guess.
|
|
|
54
54
|
online and never uses that outbox to authorize an attempt or completion. Report the acknowledged
|
|
55
55
|
record/receipt, or the actual pending/blocked state and next replay action.
|
|
56
56
|
|
|
57
|
+
## Hand-off
|
|
58
|
+
|
|
59
|
+
- When you hand a pull request to the human as ready, write one retrospective from the session
|
|
60
|
+
that did the work, before you stop, including when you delegate the pull request with
|
|
61
|
+
`/shepherd`. A native stack gets one retrospective for the whole stack, never one per layer.
|
|
62
|
+
- Give each hand-off its own `sourceEventId`, such as `handoff-pr<number>` (a stack uses its top
|
|
63
|
+
pull request's number), on both `retrospective_check` and `retrospective_save`. The default ID
|
|
64
|
+
fits only the first hand-off in a session; a second would be mistaken for it.
|
|
65
|
+
- If you are still running when the merge happens and it changes the outcome (a merge-queue
|
|
66
|
+
ejection and its fix, a follow-up push, review comments addressed after hand-off), append one
|
|
67
|
+
short note with the [blackboard skill](../blackboard/SKILL.md). Name the pull request and the
|
|
68
|
+
retrospective's source event, and give the note its own `sourceEventId`, such as
|
|
69
|
+
`merge-pr<number>`: the writer rejects the retrospective's ID reused for different content.
|
|
70
|
+
Never write a second retrospective.
|
|
71
|
+
|
|
57
72
|
Read [ci-failures](references/ci-failures.md) when the session observed CI failures, and
|
|
58
73
|
[sandbox-audit](references/sandbox-audit.md) when it hit denied or escalated commands.
|
|
59
74
|
|
|
@@ -67,7 +67,7 @@ Use when completed retrospectives or journals should become durable follow-up wo
|
|
|
67
67
|
evidence.
|
|
68
68
|
6. Draft self-contained issues with the problem, concrete proposed work, relevant areas, and
|
|
69
69
|
validation, using the [issue body template](references/issue-body.md). Route every authorized creation through
|
|
70
|
-
|
|
70
|
+
the `github-issue` skill (`skills` plugin), including its repository gate, label approval, and
|
|
71
71
|
denied-external tracking behavior.
|
|
72
72
|
7. Archive only verified records fully processed across every represented repository, and never
|
|
73
73
|
while any worktree's `outbox_status` reports a `worktreePendingCount` above 0, under the
|
|
@@ -37,4 +37,9 @@ a finding in your own words; never paste a command line or stderr, and strip any
|
|
|
37
37
|
`VAR=value` assignment, or credential-bearing URL. Checking a claim against the remote default branch
|
|
38
38
|
verifies its accuracy; it does not sanitize the text.
|
|
39
39
|
|
|
40
|
-
|
|
40
|
+
In `## Files / areas`, verify every existing path on the default branch's `HEAD`, mark each
|
|
41
|
+
proposed path `New`, and use no absolute or `..` paths.
|
|
42
|
+
|
|
43
|
+
A stop condition in an issue names a real decision for a human. Adding or changing an index, or a
|
|
44
|
+
rewrite that returns the same rows, is never one: the worker makes the change and records the plan
|
|
45
|
+
before and after.
|
|
@@ -17,8 +17,8 @@ local configuration edits or a live taxonomy mutation. Read local `AGENTS.md` fi
|
|
|
17
17
|
2. Identify automation-owned labels. Inspect local label automation before recommending a rename,
|
|
18
18
|
deletion, or rule change.
|
|
19
19
|
3. Audit aliases, ambiguity, unused labels, missing descriptions, color consistency, milestone
|
|
20
|
-
overlap, delivery gaps, and path-label coverage. Audit projects against
|
|
21
|
-
[
|
|
20
|
+
overlap, delivery gaps, and path-label coverage. Audit projects against the
|
|
21
|
+
[project rules](../organize-github-issues/SKILL.md#projects-and-milestones):
|
|
22
22
|
- A milestone theme duplicated across repositories is a candidate project.
|
|
23
23
|
- A project that holds only routine, non-initiative work is a candidate milestone. Repository
|
|
24
24
|
count is not the signal.
|
|
@@ -30,8 +30,7 @@ local configuration edits or a live taxonomy mutation. Read local `AGENTS.md` fi
|
|
|
30
30
|
need product or scheduling judgment. Applying an existing label is not taxonomy creation and
|
|
31
31
|
needs no separate approval from the authorized issue operation.
|
|
32
32
|
5. Before creating a label, stop for explicit approval of its exact repository, name, description,
|
|
33
|
-
and color. Re-fetch current state
|
|
34
|
-
[github-issue](../github-issue/SKILL.md): require `WRITE`, `MAINTAIN`, or `ADMIN` and the
|
|
33
|
+
and color. Re-fetch current state, then require `WRITE`, `MAINTAIN`, or `ADMIN` and the
|
|
35
34
|
label-specific API capability immediately before the approved mutation. `viewerCanCreateIssues`
|
|
36
35
|
applies only to issue creation. Approval for an issue or another label does not transfer.
|
|
37
36
|
|