@elvis1513/auto-coding-skill 3.0.3 → 4.0.0
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/README.md +131 -324
- package/cli/assets/agents/explorer.toml +1 -1
- package/cli/assets/agents/fixer.toml +4 -4
- package/cli/assets/agents/reviewer.toml +11 -12
- package/cli/assets/skill/SKILL.md +95 -223
- package/cli/assets/skill/data/policies/workflow-migrations-v1.json +3 -3
- package/cli/assets/skill/data/templates/ENGINEERING.md +137 -292
- package/cli/assets/skill/data/templates/bridges/AGENTS.md +26 -13
- package/cli/assets/skill/scripts/ap.py +665 -193
- package/cli/src/index.js +13 -13
- package/cli/tests/ap_concurrency_test.py +47 -14
- package/cli/tests/ap_profiles_test.py +55 -22
- package/cli/tests/index.test.js +52 -31
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -1,104 +1,14 @@
|
|
|
1
1
|
# auto-coding-skill
|
|
2
2
|
|
|
3
|
-
A
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
-
|
|
12
|
-
avoided temporary branches when they provide no isolation benefit.
|
|
13
|
-
- Fixed quoted and inline legacy gate YAML detection in CLI status.
|
|
14
|
-
|
|
15
|
-
## What changed in v3.0.2
|
|
16
|
-
|
|
17
|
-
- Added controlled synchronization for the root `AGENTS.md` workflow bridge as
|
|
18
|
-
well as the managed `ENGINEERING.md` workflow block.
|
|
19
|
-
- Migrated known legacy rules that required full local gates, verify mode, or
|
|
20
|
-
Jenkins polling during normal development while preserving project facts and
|
|
21
|
-
unrelated custom instructions.
|
|
22
|
-
- Made project status, sync, doctor, and task lifecycle commands fail closed on
|
|
23
|
-
unknown workflow instructions that conflict with the changed-scope fast gate.
|
|
24
|
-
- Removed legacy YAML escalation fields during upgrade while keeping explicit
|
|
25
|
-
full-gate commands available for user-requested diagnostics.
|
|
26
|
-
- Clarified that locked dependencies may be restored only when the configured
|
|
27
|
-
changed-scope gate actually needs them, after which only that same fast gate is
|
|
28
|
-
rerun.
|
|
29
|
-
|
|
30
|
-
## What changed in v3.0.1
|
|
31
|
-
|
|
32
|
-
- Fixed normal development to analysis → decomposition → design → development →
|
|
33
|
-
one changed-scope fast gate → push.
|
|
34
|
-
- Kept risk profiles for planning/review depth without promoting local work to a
|
|
35
|
-
standard/full gate or verify mode.
|
|
36
|
-
- Ended coding tasks immediately after safe target-branch push; Jenkins owns
|
|
37
|
-
later build/deploy work and the project owner owns acceptance.
|
|
38
|
-
- Removed repeated integration gates and all automatic post-push Jenkins/target
|
|
39
|
-
polling from `commit-push`.
|
|
40
|
-
- Required all project/Jenkins/GitLab/Nexus URLs, usernames, and direct passwords
|
|
41
|
-
under `access.*` during project initialization.
|
|
42
|
-
- Removed the shared-checkout `legacy` escape hatch; worktree isolation is now
|
|
43
|
-
mandatory for every write task.
|
|
44
|
-
- Added a structured subagent plan with parallel discovery, one-writer worktree
|
|
45
|
-
ownership, reviewer feedback loops, and main-agent Git lifecycle ownership.
|
|
46
|
-
- Enforced task-owned paths, dependency revisions, writer leases, and
|
|
47
|
-
fingerprint-bound review approvals in the task runtime.
|
|
48
|
-
- Added review, writer handoff, and conflicted-rebase resume lifecycle commands.
|
|
49
|
-
- Added planned paths and task intent to pre-development classification and
|
|
50
|
-
published a stable orchestration contract.
|
|
51
|
-
- Added controlled `ENGINEERING.md` workflow synchronization while preserving
|
|
52
|
-
project configuration and custom content.
|
|
53
|
-
|
|
54
|
-
## What changed in v3.0.0
|
|
55
|
-
|
|
56
|
-
- Isolated every write task in a registered Git worktree and task branch.
|
|
57
|
-
- Added `task-start`, `task-status`, `task-submodule-sync`, `task-integrate`,
|
|
58
|
-
`task-finish`, and `task-prune` lifecycle commands.
|
|
59
|
-
- Made `commit-push` validate the task manifest before any gate or ledger write,
|
|
60
|
-
stage only the task worktree's exact paths, and detect gate-time mutations.
|
|
61
|
-
- Added task-scoped active, closure, and evidence records to avoid shared append
|
|
62
|
-
conflicts.
|
|
63
|
-
- Serialized target-branch integration and re-ran the resolved gate after
|
|
64
|
-
updating to the latest remote target.
|
|
65
|
-
- Automatically removed integrated worktrees and local task branches, with safe
|
|
66
|
-
lease-based remote task-branch cleanup and merged-branch pruning.
|
|
67
|
-
- Initially kept a `legacy` compatibility escape hatch; v3.0.1 removes that path and
|
|
68
|
-
migrates existing configuration to mandatory worktree isolation.
|
|
69
|
-
|
|
70
|
-
## What changed in v2.2.1
|
|
71
|
-
|
|
72
|
-
- Made same-period ledger archiving update one cumulative archive-index entry
|
|
73
|
-
instead of appending duplicate month headings.
|
|
74
|
-
- Recognized Markdown-wrapped and localized settled statuses such as
|
|
75
|
-
`` `Done / PASS` `` and `Done(PASS)` during physical history archiving.
|
|
76
|
-
- Added regression coverage for repeated same-month archives and these status
|
|
77
|
-
formats.
|
|
78
|
-
|
|
79
|
-
## What changed in v2.2.0
|
|
80
|
-
|
|
81
|
-
- Added `micro`, `standard`, and `high-risk` execution profiles.
|
|
82
|
-
- `workflow.profile: auto` classifies changed work and cannot downgrade detected
|
|
83
|
-
high-risk changes.
|
|
84
|
-
- High-risk and explicit verify work now require a real `gate_full`/`full_gate`;
|
|
85
|
-
light and standard commands are no longer accepted as full-gate fallbacks.
|
|
86
|
-
- Generic structure checks are advisory by default. Projects can opt into
|
|
87
|
-
blocking enforcement.
|
|
88
|
-
- Reduced a new project scaffold from 46 files / about 10,120 lines to 20 files /
|
|
89
|
-
about 5,300 lines.
|
|
90
|
-
- Replaced duplicated repository-side Python tools with a small launcher that
|
|
91
|
-
delegates to the single project-local skill runtime.
|
|
92
|
-
- Kept only ENGINEERING, taskbook, and closure log in the default documentation
|
|
93
|
-
scaffold; all specialized documents are materialized on demand.
|
|
94
|
-
- Removed hard-coded model names from managed Agent templates. New installs
|
|
95
|
-
inherit the active client model; existing project model overrides survive sync.
|
|
96
|
-
- Added behavioral regression tests for profile resolution, strict full gates,
|
|
97
|
-
advisory structure checks, minimal scaffold budgets, on-demand docs, and Agent
|
|
98
|
-
model inheritance.
|
|
99
|
-
|
|
100
|
-
This section records historical v2 behavior. The v3.0.3 workflow above supersedes
|
|
101
|
-
its full-gate and verify-mode rules for normal development.
|
|
3
|
+
A delivery-first Codex engineering workflow:
|
|
4
|
+
|
|
5
|
+
`analysis → decomposition → necessary design → development → one final fast
|
|
6
|
+
changed-scope gate → commit/push`.
|
|
7
|
+
|
|
8
|
+
Version 4.0 replaces the 3.x governance-first defaults with progressive
|
|
9
|
+
guardrails. Clean single-writer work stays on the current branch. Worktrees,
|
|
10
|
+
parallel fixers, fingerprint review, durable design records, and stronger
|
|
11
|
+
affected-scope checks are enabled only when concurrency or risk justifies them.
|
|
102
12
|
|
|
103
13
|
## Install
|
|
104
14
|
|
|
@@ -109,285 +19,182 @@ autocoding sync --projects .
|
|
|
109
19
|
pip install pyyaml requests
|
|
110
20
|
```
|
|
111
21
|
|
|
112
|
-
|
|
113
|
-
`.agents`. `autocoding sync` installs the minimal project scaffold:
|
|
22
|
+
The project install contains:
|
|
114
23
|
|
|
115
24
|
```text
|
|
116
25
|
.agents/skills/auto-coding-skill/
|
|
117
26
|
.agents/agents/
|
|
118
27
|
docs/ENGINEERING.md
|
|
119
|
-
docs/tasks/taskbook.md
|
|
120
|
-
docs/tasks/closure-log.md
|
|
121
28
|
docs/tools/autopipeline/ap.py
|
|
29
|
+
AGENTS.md (managed bridge only; project content is preserved)
|
|
122
30
|
```
|
|
123
31
|
|
|
124
|
-
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
## Execution profiles
|
|
32
|
+
Ordinary projects no longer receive taskbook or closure logs. Existing optional
|
|
33
|
+
documents are preserved during upgrades but are not required or updated by the
|
|
34
|
+
normal workflow.
|
|
128
35
|
|
|
129
|
-
|
|
36
|
+
Fill the project/Jenkins/GitLab/Nexus URL, username, and password fields under
|
|
37
|
+
`access.*`, then configure one real fast validation command and run:
|
|
130
38
|
|
|
131
|
-
```
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
profile: auto
|
|
135
|
-
completion: push
|
|
39
|
+
```bash
|
|
40
|
+
python3 docs/tools/autopipeline/ap.py upgrade --write
|
|
41
|
+
python3 docs/tools/autopipeline/ap.py doctor
|
|
136
42
|
```
|
|
137
43
|
|
|
138
|
-
|
|
139
|
-
| --- | --- | --- | --- |
|
|
140
|
-
| `micro` | docs/tests-only or explicitly isolated work | changed/quick | pushed |
|
|
141
|
-
| `standard` | normal feature and defect work | changed/quick | pushed |
|
|
142
|
-
| `high-risk` | sensitive, broad, deploy/build, or structural work | changed/quick | pushed |
|
|
143
|
-
|
|
144
|
-
`auto` is a selector, not a fourth effective profile. Profiles affect analysis,
|
|
145
|
-
design depth, and reviewer recommendations only. They never expand the automatic
|
|
146
|
-
local gate or turn Jenkins/target verification into a completion condition.
|
|
44
|
+
Plaintext credential values are allowed by the generic workflow.
|
|
147
45
|
|
|
148
|
-
|
|
149
|
-
auto's low/normal baseline and acts as a floor for CLI overrides. Independently
|
|
150
|
-
detected high-risk signals still force `high-risk`.
|
|
46
|
+
## Adaptive development
|
|
151
47
|
|
|
152
|
-
Inspect
|
|
48
|
+
Inspect a task before writing:
|
|
153
49
|
|
|
154
50
|
```bash
|
|
155
|
-
python3 docs/tools/autopipeline/ap.py classify --scope auto
|
|
156
|
-
|
|
51
|
+
python3 docs/tools/autopipeline/ap.py classify --scope auto \
|
|
52
|
+
--planned-path backend/internal/orders/service.go \
|
|
53
|
+
--intent "fix order retry" \
|
|
54
|
+
--writers 1
|
|
157
55
|
```
|
|
158
56
|
|
|
159
|
-
|
|
160
|
-
recommended Agent roles, and a machine-readable `agent_plan` describing stages,
|
|
161
|
-
dependencies, assignment/result contracts, and lifecycle ownership.
|
|
162
|
-
|
|
163
|
-
## Parallel write isolation
|
|
57
|
+
The result includes:
|
|
164
58
|
|
|
165
|
-
|
|
166
|
-
`
|
|
167
|
-
|
|
168
|
-
|
|
59
|
+
- `execution_mode=direct`: clean checkout and one writer; stay on the current branch.
|
|
60
|
+
- `execution_mode=isolated`: dirty checkout, explicit isolation, or multiple writers.
|
|
61
|
+
- `execution_mode=none`: no task signal or change; create no branch/worktree.
|
|
62
|
+
- `review_required` and `design_required`: risk-based escalation decisions.
|
|
63
|
+
- an adaptive agent plan that does not force fan-out for ordinary work.
|
|
169
64
|
|
|
170
|
-
|
|
171
|
-
concurrency:
|
|
172
|
-
isolation: adaptive
|
|
173
|
-
base_ref: origin/dev
|
|
174
|
-
target_branch: dev
|
|
175
|
-
branch_prefix: codex/
|
|
176
|
-
worktree_root: ../.worktrees
|
|
177
|
-
cleanup_merged: true
|
|
178
|
-
delete_remote_branch: true
|
|
179
|
-
disposable_ignored: []
|
|
180
|
-
```
|
|
65
|
+
Use a machine-enforced task lifecycle when useful:
|
|
181
66
|
|
|
182
67
|
```bash
|
|
183
|
-
python3 docs/tools/autopipeline/ap.py task-start T0001
|
|
184
|
-
|
|
185
|
-
python3 docs/tools/autopipeline/ap.py
|
|
186
|
-
|
|
187
|
-
python3 docs/tools/autopipeline/ap.py task-review T0001 --verdict approved --diff-fingerprint "$SHA256"
|
|
188
|
-
python3 docs/tools/autopipeline/ap.py task-handoff T0001 --from "$FIXER" --to "$CODEX_THREAD_ID" --generation 1
|
|
189
|
-
python3 docs/tools/autopipeline/ap.py commit-push T0001 --writer "$CODEX_THREAD_ID" --msg "T0001: summary"
|
|
190
|
-
python3 docs/tools/autopipeline/ap.py task-integrate T0001 --writer "$CODEX_THREAD_ID"
|
|
68
|
+
python3 docs/tools/autopipeline/ap.py task-start T0001 \
|
|
69
|
+
--owned-path backend/internal/orders
|
|
70
|
+
python3 docs/tools/autopipeline/ap.py commit-push T0001 \
|
|
71
|
+
--msg "T0001: fix order retry"
|
|
191
72
|
```
|
|
192
73
|
|
|
193
|
-
|
|
194
|
-
manifest
|
|
195
|
-
|
|
196
|
-
|
|
197
|
-
Before upgrading a v3.0.0 project, finish and clean every registered in-flight
|
|
198
|
-
task with its currently installed runtime. `autocoding sync` refuses to replace
|
|
199
|
-
that runtime while a schema-1 task remains, because 3.0.1 cannot safely infer
|
|
200
|
-
its path ownership, dependencies, writer lease, or review state.
|
|
201
|
-
|
|
202
|
-
`commit-push` runs the only local gate. `task-integrate` is the rest of the same
|
|
203
|
-
push stage: it fetches/rebases, CAS-pushes the configured target, confirms the
|
|
204
|
-
remote SHA, and cleans up without repeating the gate. Successful integration
|
|
205
|
-
ends the coding task; do not wait for Jenkins, deployment, or acceptance results.
|
|
206
|
-
The task commit runs project commit hooks once. Its internal backup-branch push
|
|
207
|
-
skips the pre-push hook, while the final target-branch push runs that hook once.
|
|
208
|
-
Integration does not create a second evidence commit.
|
|
209
|
-
|
|
210
|
-
Successful integration removes the clean worktree and merged local branch, and
|
|
211
|
-
deletes the merged remote task branch by default. `task-finish T0001` retries
|
|
212
|
-
cleanup for one integrated task; `task-prune` removes registered merged tasks
|
|
213
|
-
left behind. Dirty worktrees and unmerged branches are never removed. Integration
|
|
214
|
-
does not update the primary checkout; pull it explicitly when its local state is
|
|
215
|
-
ready. Cleanup also refuses unknown ignored files such as local secrets; list
|
|
216
|
-
only disposable project cache/build paths under `concurrency.disposable_ignored`.
|
|
217
|
-
Initialized submodules are recursively checked before forced task-worktree
|
|
218
|
-
removal: they must be clean and contain no unknown ignored data, local-only
|
|
219
|
-
commits, unmirrored local branches, or additional linked worktrees. Their
|
|
220
|
-
remotes are refreshed before that decision. A durable snapshot
|
|
221
|
-
of refs and reflog commits is stored under Git's
|
|
222
|
-
`auto-coding-skill/submodule-recovery` state before forced worktree removal, so
|
|
223
|
-
a remote deletion race cannot destroy the last copy of a commit. Cleanup never
|
|
224
|
-
deinitializes the primary checkout's shared submodule configuration.
|
|
225
|
-
`task-start` enables Git worktree-scoped config and seeds each task's submodule
|
|
226
|
-
URLs. After changing `.gitmodules`, run `task-submodule-sync` before initializing
|
|
227
|
-
or syncing modules. Relative URLs follow Git's current-worktree default-remote
|
|
228
|
-
rules, including task bases whose `.gitmodules` differs from the control checkout.
|
|
229
|
-
Shared/common submodule config changes are reported and never overwritten.
|
|
230
|
-
Residual Git directories from modules manually deinitialized inside a task block
|
|
231
|
-
forced cleanup until they are reinitialized or recovered.
|
|
232
|
-
|
|
233
|
-
## Gate configuration
|
|
74
|
+
On a clean single-writer checkout, `task-start` records a lightweight direct
|
|
75
|
+
manifest in the Git common directory and creates no branch or worktree.
|
|
76
|
+
`commit-push` runs the final gate, commits, and pushes the current target branch.
|
|
77
|
+
If no diff was produced, it clears the manifest without commit or push.
|
|
234
78
|
|
|
235
|
-
|
|
236
|
-
commands:
|
|
237
|
-
gate_changed: "git diff --check"
|
|
79
|
+
Dirty or parallel work receives an isolated task branch/worktree:
|
|
238
80
|
|
|
239
|
-
|
|
240
|
-
|
|
241
|
-
|
|
242
|
-
|
|
243
|
-
|
|
244
|
-
|
|
81
|
+
```bash
|
|
82
|
+
python3 docs/tools/autopipeline/ap.py task-start T0002 \
|
|
83
|
+
--owned-path backend --writers 2 --review-required
|
|
84
|
+
# implement in the printed worktree
|
|
85
|
+
python3 docs/tools/autopipeline/ap.py task-review T0002 \
|
|
86
|
+
--verdict approved --diff-fingerprint "$SHA256"
|
|
87
|
+
python3 docs/tools/autopipeline/ap.py commit-push T0002 \
|
|
88
|
+
--msg "T0002: bounded change"
|
|
89
|
+
python3 docs/tools/autopipeline/ap.py task-integrate T0002
|
|
245
90
|
```
|
|
246
91
|
|
|
247
|
-
|
|
248
|
-
|
|
249
|
-
|
|
250
|
-
|
|
251
|
-
For Node projects, a new scaffold selects `npm run test:changed` only when that
|
|
252
|
-
dedicated quick script exists. It never promotes ordinary `npm test`, builds, or
|
|
253
|
-
full regression into the automatic changed gate. Standard/full commands may be
|
|
254
|
-
kept as explicit diagnostics, but normal development does not invoke them.
|
|
92
|
+
Integration serializes the target push and removes clean merged worktrees and
|
|
93
|
+
temporary branches. Unknown changes, unmerged history, unsafe ignored data, or
|
|
94
|
+
dirty submodules block cleanup rather than being discarded.
|
|
255
95
|
|
|
256
|
-
##
|
|
96
|
+
## Real changed-scope validation
|
|
257
97
|
|
|
258
|
-
|
|
259
|
-
function-size signals, and import-direction heuristics, but it is not universally
|
|
260
|
-
authoritative:
|
|
98
|
+
Risk classification and validation execution are deliberately separate:
|
|
261
99
|
|
|
262
100
|
```yaml
|
|
263
|
-
|
|
264
|
-
|
|
265
|
-
|
|
266
|
-
|
|
267
|
-
|
|
268
|
-
|
|
269
|
-
|
|
270
|
-
|
|
271
|
-
|
|
272
|
-
|
|
273
|
-
|
|
274
|
-
|
|
275
|
-
|
|
276
|
-
|
|
277
|
-
|
|
278
|
-
|
|
279
|
-
|
|
280
|
-
|
|
281
|
-
|
|
282
|
-
|
|
283
|
-
python3 docs/tools/autopipeline/ap.py scaffold deployment --write
|
|
284
|
-
python3 docs/tools/autopipeline/ap.py scaffold bugs --write
|
|
285
|
-
python3 docs/tools/autopipeline/ap.py scaffold all --write
|
|
101
|
+
commands:
|
|
102
|
+
backend_fast: "cd backend && go test ./internal/orders/..."
|
|
103
|
+
frontend_fast: "cd frontend && npm run test:changed"
|
|
104
|
+
|
|
105
|
+
validation:
|
|
106
|
+
on_unmapped: error
|
|
107
|
+
routes:
|
|
108
|
+
- name: backend
|
|
109
|
+
paths: ["backend/**", "contracts/**"]
|
|
110
|
+
commands: [backend_fast]
|
|
111
|
+
- name: frontend
|
|
112
|
+
paths: ["frontend/**"]
|
|
113
|
+
commands: [frontend_fast]
|
|
114
|
+
|
|
115
|
+
risk:
|
|
116
|
+
rules:
|
|
117
|
+
- name: auth
|
|
118
|
+
paths: ["backend/**/auth/**"]
|
|
119
|
+
profile: high-risk
|
|
120
|
+
review: required
|
|
286
121
|
```
|
|
287
122
|
|
|
288
|
-
|
|
289
|
-
|
|
290
|
-
|
|
123
|
+
Every path may match multiple routes. All referenced commands are collected in
|
|
124
|
+
configuration order, de-duplicated, and executed once. Unmapped code and missing
|
|
125
|
+
commands fail before staging. Documentation-only changes may use the built-in
|
|
126
|
+
diff check. `git diff --check` remains an additional hygiene check and is never
|
|
127
|
+
treated as business validation.
|
|
291
128
|
|
|
292
|
-
|
|
129
|
+
Check coverage without running project commands:
|
|
293
130
|
|
|
294
131
|
```bash
|
|
295
|
-
python3
|
|
132
|
+
python3 docs/tools/autopipeline/ap.py validation-map-check --path contracts/api.yaml
|
|
133
|
+
python3 docs/tools/autopipeline/ap.py validation-map-check --tracked
|
|
296
134
|
```
|
|
297
135
|
|
|
298
|
-
|
|
299
|
-
|
|
300
|
-
|
|
301
|
-
|
|
302
|
-
model automatically.
|
|
303
|
-
|
|
304
|
-
Existing project-local `model = "..."` lines are treated as explicit overrides:
|
|
305
|
-
|
|
306
|
-
- `status` reports them but does not mark the project stale for model-only drift.
|
|
307
|
-
- `sync` updates managed instructions while preserving the override.
|
|
308
|
-
- `sync --reset-agent-models` removes managed-role overrides and returns to
|
|
309
|
-
client inheritance.
|
|
310
|
-
- Custom Agent files are always preserved byte-for-byte.
|
|
311
|
-
|
|
312
|
-
The effective profile emits an executable collaboration shape:
|
|
313
|
-
|
|
314
|
-
- micro: main Agent only unless useful independent work exceeds dispatch overhead
|
|
315
|
-
- standard/high-risk: main decomposition → parallel justified explorer/docs/browser
|
|
316
|
-
discovery → main design → dependency waves of isolated fixers → read-only
|
|
317
|
-
reviewers → main fast gate/integration, followed by final push/cleanup
|
|
318
|
-
|
|
319
|
-
Only dependency-free fixer units with explicitly non-overlapping paths may run
|
|
320
|
-
in parallel. A dependent writer starts after its prerequisite is integrated.
|
|
321
|
-
Subagents do not commit, push, integrate, clean branches, or run the project gate.
|
|
322
|
-
Reviewer findings return to the owning fixer. Verdicts bind to a diff fingerprint,
|
|
323
|
-
so any edit requires re-review before the main Agent may run the gate.
|
|
324
|
-
|
|
325
|
-
## Required access configuration
|
|
136
|
+
Focused tests may be run and rerun during implementation. Only the final routed
|
|
137
|
+
closure gate is limited to one stable-diff run. Full regression, Docker, builds,
|
|
138
|
+
Jenkins, deployment, API verification, and target checks remain explicit
|
|
139
|
+
diagnostics outside normal closure.
|
|
326
140
|
|
|
327
|
-
|
|
328
|
-
`access.gitlab`, and `access.nexus` in `docs/ENGINEERING.md`. Existing projects
|
|
329
|
-
must run `ap.py upgrade --write` to merge newly required fields into their manual
|
|
330
|
-
configuration. Fill every URL, username, and direct password during
|
|
331
|
-
initialization as an inline YAML string; quote values that resemble numbers,
|
|
332
|
-
dates, booleans, or YAML collections. `status` rejects blank/TODO fields;
|
|
333
|
-
`doctor` and `task-start`
|
|
334
|
-
also validate URL shape locally. These access checks never contact the listed
|
|
335
|
-
service endpoints; after validation, `task-start` may still fetch the configured
|
|
336
|
-
Git remote unless `--no-fetch` is used. Configuration presence does not enable
|
|
337
|
-
Jenkins/build/deploy verification.
|
|
141
|
+
## Risk and subagent policy
|
|
338
142
|
|
|
339
|
-
|
|
143
|
+
- Micro and standard work default to the main agent.
|
|
144
|
+
- Read-only explorer/docs/browser roles run only for independent questions with
|
|
145
|
+
clear value.
|
|
146
|
+
- Parallel fixers require separate worktrees and non-overlapping paths.
|
|
147
|
+
- Reviewer fingerprint approval is required for high-risk, cross-module,
|
|
148
|
+
explicitly configured, or parallel integration work.
|
|
149
|
+
- DD/ADR is created only for lasting cross-module, API, data, security,
|
|
150
|
+
deployment, or key user-flow decisions.
|
|
151
|
+
- Historical debt does not block product work unless the current change worsens it.
|
|
340
152
|
|
|
341
|
-
|
|
342
|
-
|
|
343
|
-
|
|
344
|
-
python3 docs/tools/autopipeline/ap.py light-gate --scope auto --explain
|
|
345
|
-
python3 docs/tools/autopipeline/ap.py structure-check --scope auto
|
|
346
|
-
python3 docs/tools/autopipeline/ap.py task-start T0001 --owned-path src --writer "$FIXER"
|
|
347
|
-
python3 docs/tools/autopipeline/ap.py task-status T0001
|
|
348
|
-
python3 docs/tools/autopipeline/ap.py task-submodule-sync T0001
|
|
349
|
-
python3 docs/tools/autopipeline/ap.py task-review T0001 --verdict approved --diff-fingerprint "$SHA256"
|
|
350
|
-
python3 docs/tools/autopipeline/ap.py task-handoff T0001 --from "$FIXER" --to "$CODEX_THREAD_ID" --generation 1
|
|
351
|
-
python3 docs/tools/autopipeline/ap.py docs-ledger-check
|
|
352
|
-
python3 docs/tools/autopipeline/ap.py gate-profile
|
|
353
|
-
python3 docs/tools/autopipeline/ap.py commit-push T0001 --writer "$CODEX_THREAD_ID" --msg "T0001: summary"
|
|
354
|
-
python3 docs/tools/autopipeline/ap.py task-integrate T0001 --writer "$CODEX_THREAD_ID"
|
|
355
|
-
python3 docs/tools/autopipeline/ap.py task-finish T0001
|
|
356
|
-
python3 docs/tools/autopipeline/ap.py task-prune
|
|
357
|
-
```
|
|
153
|
+
The main agent owns architecture, final validation, Git closure, ordered
|
|
154
|
+
integration, push, and cleanup. Push ends the coding task; later CI/acceptance is
|
|
155
|
+
handled only through a separately requested diagnostic task.
|
|
358
156
|
|
|
359
157
|
## Upgrade and multi-project sync
|
|
360
158
|
|
|
361
|
-
|
|
362
|
-
|
|
363
|
-
|
|
364
|
-
python3 docs/tools/autopipeline/ap.py upgrade --dry-run
|
|
365
|
-
python3 docs/tools/autopipeline/ap.py upgrade --write
|
|
159
|
+
Finish all in-flight schema-1/schema-2 registered tasks using their installed 3.x
|
|
160
|
+
runtime before syncing 4.0. Batch sync fails before any writes when it finds an
|
|
161
|
+
incompatible active task.
|
|
366
162
|
|
|
163
|
+
```bash
|
|
367
164
|
autocoding status --projects /path/a,/path/b
|
|
368
165
|
autocoding sync --projects /path/a,/path/b --dry-run
|
|
166
|
+
autocoding sync --projects /path/a,/path/b
|
|
369
167
|
```
|
|
370
168
|
|
|
371
|
-
|
|
372
|
-
|
|
373
|
-
|
|
374
|
-
|
|
375
|
-
|
|
376
|
-
|
|
377
|
-
|
|
378
|
-
|
|
379
|
-
|
|
380
|
-
|
|
381
|
-
|
|
169
|
+
Sync replaces the managed Skill directory, so missing files are restored and
|
|
170
|
+
obsolete managed files are removed. It preserves project frontmatter, access
|
|
171
|
+
values, custom agents, explicit model overrides, optional documents, and content
|
|
172
|
+
outside managed AGENTS/ENGINEERING blocks.
|
|
173
|
+
|
|
174
|
+
## What changed in 4.0.0
|
|
175
|
+
|
|
176
|
+
- Added real `direct` and `isolated` runtime execution modes.
|
|
177
|
+
- Stopped creating branches/worktrees for clean serial or no-diff work.
|
|
178
|
+
- Added multi-match `validation.routes`, stable command de-duplication,
|
|
179
|
+
fail-closed unmapped code, and `validation-map-check`.
|
|
180
|
+
- Separated `risk.rules` from executable validation.
|
|
181
|
+
- Made ordinary tasks main-agent-first and review/design conditional.
|
|
182
|
+
- Kept advanced worktree ownership, dependency SHA, lease, fingerprint,
|
|
183
|
+
integration, submodule safety, and branch cleanup for parallel/high-risk work.
|
|
184
|
+
- Removed taskbook, closure, evidence, and active-task documents from the default
|
|
185
|
+
scaffold and normal closure path.
|
|
186
|
+
- Changed structure/debt policy to no-new-debt and kept full/CI/runtime checks as
|
|
187
|
+
explicit diagnostics.
|
|
188
|
+
- Added schema-3 task manifests and atomic sync refusal for in-flight pre-4.0 tasks.
|
|
189
|
+
|
|
190
|
+
## Maintainer commands
|
|
382
191
|
|
|
383
192
|
```bash
|
|
384
|
-
npm run
|
|
385
|
-
npm test
|
|
193
|
+
npm run sync-assets
|
|
386
194
|
npm run release:check
|
|
387
195
|
```
|
|
388
196
|
|
|
389
|
-
|
|
390
|
-
|
|
391
|
-
TOML, runs the broader regressions, and performs `npm pack --dry-run`.
|
|
197
|
+
`release:check` validates source/assets, Python 3.11 grammar, managed Agent TOML,
|
|
198
|
+
CLI/profile/concurrency regressions, and the npm package contents.
|
|
392
199
|
|
|
393
200
|
License: MIT.
|
|
@@ -9,7 +9,7 @@ developer_instructions = """
|
|
|
9
9
|
工作要求:
|
|
10
10
|
1. 优先用 rg / git / 项目脚本快速定位真实入口,再向下追踪调用链。
|
|
11
11
|
2. 先读项目已有文档、配置、路由、任务记录;涉及结构/优化时,仅在结构标准、健康基线或优化 backlog 已存在时读取,不因可选文档缺失而阻塞。
|
|
12
|
-
3. 必要时运行 `ap.py classify --scope auto
|
|
12
|
+
3. 必要时运行 `ap.py classify --scope auto`,说明执行模式、风险和是否确实需要设计/reviewer;普通任务默认主代理直接完成,本地 gate 始终保持 changed-scope。
|
|
13
13
|
4. 输出根因时说明当前代码应归属的层级、现有同类模块、可复用 helper / 组件 / 脚本,以及是否触及 `structure.layer_rules`。
|
|
14
14
|
5. 如果根因依赖外部库、框架或版本行为,标记需要 docs_researcher / Context7 继续核对,不要凭记忆猜。
|
|
15
15
|
6. 输出内容必须尽量具体到:
|
|
@@ -7,7 +7,7 @@ developer_instructions = """
|
|
|
7
7
|
你负责小而准的实现修改。
|
|
8
8
|
|
|
9
9
|
工作要求:
|
|
10
|
-
1. 只在问题已经相对明确,并收到 task_id、execution_mode、owned_paths、depends_on 和 acceptance
|
|
10
|
+
1. 只在问题已经相对明确,并收到 task_id、execution_mode、owned_paths、depends_on 和 acceptance 后再动手;只有 delegated/isolated 工作才要求完整任务元数据。
|
|
11
11
|
2. direct 模式只用于单写入者且主代理确认当前 checkout 干净的当前分支;isolated 模式必须确认当前目录和 task_branch 与分配的注册 worktree 一致。不满足时停止并上报。
|
|
12
12
|
3. 一个 worktree 只能有一个写入者。只修改 owned_paths,不进入或修改其他任务工作树;发现未知改动立即停止,不 restore/reset/stash/clean。direct 模式期间主代理不得并发编辑同一 checkout。
|
|
13
13
|
4. 坚持“最小可辩护修改”原则。
|
|
@@ -18,11 +18,11 @@ developer_instructions = """
|
|
|
18
18
|
9. 新增工具、并发/缓存/请求封装、格式转换、权限判断、校验逻辑前,先搜索既有 helper、库、组件和脚本。
|
|
19
19
|
10. 如果修改依赖外部 API / 版本行为,先让 docs_researcher / 文档 MCP 兜底确认。
|
|
20
20
|
11. UI 实际验收由项目负责人在推送后处理;只有用户明确要求诊断时才交给 browser_debugger。
|
|
21
|
-
12.
|
|
22
|
-
13.
|
|
21
|
+
12. 高风险、跨模块、并行或项目显式要求的修改交给 reviewer;普通串行修复不强制 reviewer。
|
|
22
|
+
13. 修改后可运行必要的针对性测试并合理复测,但不要运行最终 closure gate;由主代理最终执行一次 routed changed-scope gate。不要叠加 docs-ledger、全量测试、构建、Docker、Jenkins 或目标环境验证。
|
|
23
23
|
14. 不提交、不推送、不集成、不清理分支;等待 reviewer 和主代理收口。
|
|
24
24
|
15. 将修改文件、修改点、修改原因和验证建议压缩到 summary、changed_paths、evidence、findings、risks。
|
|
25
|
-
16. reviewer
|
|
25
|
+
16. 任务需要 reviewer 时,其修改意见只由当前 owning fixer 串行处理;修改完成后重新审查,旧审批自动失效。
|
|
26
26
|
17. 如发现问题超出小修范围,要立即停止并上报,不要自行扩大战场。
|
|
27
27
|
18. 目标分支推送成功即结束,不等待或处理后续 Jenkins、构建、部署和实际验收结果。
|
|
28
28
|
19. 最终只返回一个 JSON 对象,不要 Markdown 或代码围栏。对象必须符合 `.agents/skills/auto-coding-skill/data/contracts/orchestration-v1.schema.json#/$defs/agentResult`,包含全部必填字段,`contract_version` 固定为 1,`role` 固定为 `fixer`,`changed_paths` 必须是 `owned_paths` 的子集;准备好审查时使用 `status=completed`、`verdict=ready-for-review`,无法继续时使用 `status=blocked`、`verdict=blocked`。
|
|
@@ -9,20 +9,19 @@ developer_instructions = """
|
|
|
9
9
|
工作要求:
|
|
10
10
|
1. 只审查主代理给定的 task_id、base_sha、diff_base、diff_head、diff_fingerprint 和 owning_fixer;确认 diff 稳定后再开始。
|
|
11
11
|
2. 优先检查:正确性、安全性、边界条件、异常路径、并发风险、事务一致性、缓存一致性、兼容性。
|
|
12
|
-
3. 结构/优化 review
|
|
13
|
-
4.
|
|
14
|
-
5.
|
|
15
|
-
6.
|
|
16
|
-
7.
|
|
17
|
-
8.
|
|
18
|
-
9. 每条问题尽量包含:
|
|
12
|
+
3. 结构/优化 review 仅在已有 baseline/backlog 时读取;可选文档缺失不构成 blocker,不重复报告 accepted debt。
|
|
13
|
+
4. 检查实际 diff 和已执行验证是否一致;普通任务不要求 taskbook、closure 或 evidence 文档。
|
|
14
|
+
5. 涉及鉴权、权限、支付、文件上传下载、部署、依赖或数据边界时,优先使用可用的安全扫描 / security review 能力辅助复核。
|
|
15
|
+
6. 以 git diff、相关测试、接口契约、真实运行证据、结构标准为基础,不凭风格偏好输出问题。
|
|
16
|
+
7. 优先输出真实问题,不要输出样式洁癖式意见。
|
|
17
|
+
8. 每条问题尽量包含:
|
|
19
18
|
- 问题点
|
|
20
19
|
- 影响范围
|
|
21
20
|
- 复现条件
|
|
22
21
|
- 建议修法
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
22
|
+
9. 发现测试不足时,指出应补哪些测试或验证路径。
|
|
23
|
+
10. 结论必须是 approved 或 changes-requested;changes-requested 只返回 owning_fixer,修改后必须基于新 diff 重审。
|
|
24
|
+
11. 不修改代码,不提交、不推送、不集成、不清理分支;审查不扩展本地门禁。
|
|
25
|
+
12. 最终只返回一个 JSON 对象,不要 Markdown 或代码围栏。对象必须符合 `.agents/skills/auto-coding-skill/data/contracts/orchestration-v1.schema.json#/$defs/agentResult`,包含全部必填字段,`contract_version` 固定为 1,`role` 固定为 `reviewer`,`changed_paths` 固定为空数组,`diff_fingerprint` 必须原样返回;审查完成时 `status=completed` 且 `verdict` 只能是 `approved` 或 `changes-requested`,无法继续时使用 `status=blocked`、`verdict=blocked`。findings 按 P0/P1/P2/P3 排序。
|
|
26
|
+
13. 目标分支推送成功后,不跟踪 Jenkins、部署或项目负责人的实际验收。
|
|
28
27
|
"""
|