@elvis1513/auto-coding-skill 3.0.4 → 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 -329
- 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 +2 -2
- 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
|
@@ -1,265 +1,137 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: auto-coding-skill
|
|
3
|
-
description:
|
|
3
|
+
description: Delivery-first engineering workflow for repository changes. Use for analysis, task decomposition, necessary design, implementation, fast changed-scope validation, safe commit/push, adaptive Git isolation, parallel writer coordination, and temporary branch cleanup. Keep clean single-writer work on the current branch; escalate to worktrees, subagents, review, or stronger affected-scope checks only when risk or concurrency justifies them.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Auto Coding Skill
|
|
7
7
|
|
|
8
|
-
|
|
9
|
-
gate → push workflow. The project keeps one manual configuration source:
|
|
10
|
-
`docs/ENGINEERING.md`.
|
|
8
|
+
Deliver changes through:
|
|
11
9
|
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
The main agent decomposes the task before dispatch. Run independent read-only
|
|
15
|
-
discovery roles in parallel when the runtime supports them. A single serial
|
|
16
|
-
writer uses the current branch when its checkout is clean. Dirty checkouts and
|
|
17
|
-
parallel writers use one registered worktree per fixer; never share a write
|
|
18
|
-
worktree between agents.
|
|
10
|
+
`analysis → decomposition → necessary design → development → one final fast
|
|
11
|
+
changed-scope gate → commit/push`.
|
|
19
12
|
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
autocoding sync --projects .
|
|
25
|
-
pip install pyyaml requests
|
|
26
|
-
```
|
|
27
|
-
|
|
28
|
-
New projects receive a minimal scaffold: the project-local skill, managed role
|
|
29
|
-
templates, `docs/ENGINEERING.md`, taskbook, closure log, and a small compatibility
|
|
30
|
-
launcher. Optional design, API, review, testing, deployment, and bug documents
|
|
31
|
-
are created only with `ap.py scaffold <group> --write`.
|
|
32
|
-
|
|
33
|
-
For existing projects:
|
|
34
|
-
|
|
35
|
-
```bash
|
|
36
|
-
autocoding sync --projects .
|
|
37
|
-
python3 docs/tools/autopipeline/ap.py upgrade --dry-run
|
|
38
|
-
python3 docs/tools/autopipeline/ap.py upgrade --write
|
|
39
|
-
```
|
|
40
|
-
|
|
41
|
-
Upgrade preserves project documents, custom agents, and explicit local model
|
|
42
|
-
overrides. Managed agents without a `model` inherit the current client model.
|
|
43
|
-
Initialization is incomplete until every URL, username, and direct password under
|
|
44
|
-
`access.*` is filled in `docs/ENGINEERING.md` and `doctor` passes.
|
|
13
|
+
Read `docs/ENGINEERING.md` for project facts, access values, risk rules, and
|
|
14
|
+
validation routes. Treat target-branch push as coding completion. Do not poll or
|
|
15
|
+
fix Jenkins, deployment, or owner acceptance unless the user opens a separate
|
|
16
|
+
diagnostic task.
|
|
45
17
|
|
|
46
|
-
##
|
|
18
|
+
## Choose the lightest safe path
|
|
47
19
|
|
|
48
|
-
|
|
49
|
-
resolves to exactly one execution profile:
|
|
20
|
+
Inspect the checkout before writing:
|
|
50
21
|
|
|
51
|
-
-
|
|
52
|
-
-
|
|
53
|
-
|
|
22
|
+
- Use the current branch for one writer when the checkout is clean.
|
|
23
|
+
- Use an isolated task branch/worktree when unrelated changes already exist,
|
|
24
|
+
when more than one writer will run, or when the project explicitly requires it.
|
|
25
|
+
- Use one writer per worktree and non-overlapping owned paths.
|
|
26
|
+
- Create no temporary branch merely to analyze a task or when no diff is produced.
|
|
27
|
+
- Never restore, reset, stash, clean, or modify unknown user/task changes.
|
|
54
28
|
|
|
55
|
-
|
|
56
|
-
Run exactly one changed-scope fast local gate for every profile. Keep standard/full
|
|
57
|
-
regression, structure scans, Docker, API verification, Jenkins, deployment, and
|
|
58
|
-
target checks as explicit diagnostics outside the default development flow.
|
|
59
|
-
|
|
60
|
-
Run the configuration and impact preflight:
|
|
29
|
+
Classify planned work before development when impact is unclear:
|
|
61
30
|
|
|
62
31
|
```bash
|
|
63
|
-
python3 docs/tools/autopipeline/ap.py
|
|
64
|
-
|
|
65
|
-
# Before development, add repeatable --planned-path values and either --intent
|
|
66
|
-
# or --intent-file when the working tree does not yet describe the task.
|
|
32
|
+
python3 docs/tools/autopipeline/ap.py classify --scope auto \
|
|
33
|
+
--planned-path <PATH> --intent "<intent>" [--writers <N>]
|
|
67
34
|
```
|
|
68
35
|
|
|
69
|
-
`
|
|
70
|
-
|
|
71
|
-
|
|
36
|
+
`execution_mode=direct` means stay on the current branch.
|
|
37
|
+
`execution_mode=isolated` means start registered worktrees. `execution_mode=none`
|
|
38
|
+
means do not create Git state.
|
|
72
39
|
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
For one serial writer, inspect the current checkout before creating anything. If
|
|
76
|
-
it is clean, use its current branch directly. If it already has changes, or two
|
|
77
|
-
or more writers will run concurrently, preserve the checkout and use one
|
|
78
|
-
registered task branch/worktree per writer. Read-only discovery may stay in the
|
|
79
|
-
primary worktree. A worktree has exactly one writer; no other agent may edit it
|
|
80
|
-
while that writer is active. The lifecycle commands below are for isolated mode.
|
|
40
|
+
Use the runtime-supported lifecycle when a machine-enforced task boundary helps:
|
|
81
41
|
|
|
82
42
|
```bash
|
|
83
|
-
python3 docs/tools/autopipeline/ap.py task-start
|
|
84
|
-
--owned-path
|
|
85
|
-
#
|
|
86
|
-
python3 docs/tools/autopipeline/ap.py
|
|
87
|
-
|
|
88
|
-
python3 docs/tools/autopipeline/ap.py task-
|
|
89
|
-
--verdict approved --diff-fingerprint <SHA256> --reviewer <REVIEWER>
|
|
90
|
-
python3 docs/tools/autopipeline/ap.py task-handoff <TASK_ID> \
|
|
91
|
-
--from <WRITER> --to <WRITER> [--generation <N>]
|
|
92
|
-
python3 docs/tools/autopipeline/ap.py commit-push <TASK_ID> \
|
|
93
|
-
--msg "<TASK_ID>: <summary>" [--writer <WRITER>]
|
|
94
|
-
python3 docs/tools/autopipeline/ap.py task-integrate <TASK_ID>
|
|
95
|
-
# After resolving an integration rebase conflict:
|
|
96
|
-
python3 docs/tools/autopipeline/ap.py task-resume <TASK_ID>
|
|
43
|
+
python3 docs/tools/autopipeline/ap.py task-start T0001 \
|
|
44
|
+
--owned-path src [--writers 2] [--isolated] [--review-required]
|
|
45
|
+
# Work in the path printed by task-start.
|
|
46
|
+
python3 docs/tools/autopipeline/ap.py commit-push T0001 --msg "T0001: summary"
|
|
47
|
+
# Isolated tasks only:
|
|
48
|
+
python3 docs/tools/autopipeline/ap.py task-integrate T0001
|
|
97
49
|
```
|
|
98
50
|
|
|
99
|
-
`
|
|
100
|
-
|
|
101
|
-
|
|
102
|
-
|
|
103
|
-
|
|
104
|
-
|
|
105
|
-
|
|
106
|
-
worktree and may stage only owned paths. If unknown changes appear, stop and
|
|
107
|
-
report them. Never restore, reset, stash, clean, or otherwise modify another
|
|
108
|
-
task's or the user's changes.
|
|
51
|
+
Direct `commit-push` runs the final gate and pushes the current target branch.
|
|
52
|
+
If the task has no diff, it clears its machine state without commit or push.
|
|
53
|
+
Isolated `commit-push` pushes the task branch; `task-integrate` serializes the
|
|
54
|
+
target push and removes clean merged temporary worktrees and branches. Use
|
|
55
|
+
`task-finish` or `task-prune` only for safe lifecycle cleanup.
|
|
56
|
+
|
|
57
|
+
## Scale design and review by risk
|
|
109
58
|
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
`commit-push` and `task-integrate` require a current approval for the current
|
|
113
|
-
fingerprint and verify prerequisite SHAs. If integration enters a rebase conflict,
|
|
114
|
-
resolve it in the registered worktree, continue or abort the rebase as instructed,
|
|
115
|
-
then run `task-resume`; do not bypass the conflicted manifest state.
|
|
59
|
+
Use `micro`, `standard`, and `high-risk` only to scale reasoning and guardrails;
|
|
60
|
+
never use them to trigger a full local repository gate automatically.
|
|
116
61
|
|
|
117
|
-
|
|
118
|
-
|
|
119
|
-
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
|
|
123
|
-
|
|
62
|
+
- Keep ordinary micro/standard work main-agent-only unless delegation has a
|
|
63
|
+
concrete latency or expertise benefit.
|
|
64
|
+
- Create DD/ADR only for lasting cross-module, API, data, security, deployment,
|
|
65
|
+
or key user-flow decisions.
|
|
66
|
+
- Require independent fingerprinted review for high-risk, cross-module,
|
|
67
|
+
explicitly configured, or parallel integration work.
|
|
68
|
+
- Route blocking review findings back to the owning writer and invalidate the
|
|
69
|
+
approval after any content change or rebase.
|
|
124
70
|
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
|
|
128
|
-
tasks in bulk. Refuse cleanup when a worktree is dirty or a branch is unmerged.
|
|
129
|
-
Do not update the primary checkout during integration; pull it explicitly when
|
|
130
|
-
its user-owned state is ready. Treat unknown ignored files as user data and
|
|
131
|
-
block cleanup; allow only explicitly disposable cache/build paths. Before a
|
|
132
|
-
forced task-worktree removal, recursively require every initialized submodule
|
|
133
|
-
to be clean and contain no unknown ignored data, local-only history, or
|
|
134
|
-
unmirrored local branch. Block cleanup when the submodule has another linked
|
|
135
|
-
worktree or its remotes cannot be refreshed. Before the validated forced removal,
|
|
136
|
-
persist its refs and reflog commits in the Git common directory's managed
|
|
137
|
-
submodule-recovery store so a remote race cannot erase the final copy. Never run
|
|
138
|
-
submodule deinit from a linked task worktree because its shared config can alter
|
|
139
|
-
the primary checkout.
|
|
71
|
+
Historical debt does not block normal delivery. Block only new or worsened P0/P1
|
|
72
|
+
issues. Handle repository-wide governance through an explicit task and optional
|
|
73
|
+
baseline/backlog.
|
|
140
74
|
|
|
141
|
-
|
|
142
|
-
URLs. After editing `.gitmodules`, run `task-submodule-sync` before submodule
|
|
143
|
-
initialization or sync. Resolve relative URLs with Git's current-worktree
|
|
144
|
-
default-remote semantics, not the integration remote. If shared/common submodule
|
|
145
|
-
config differs from the task-start snapshot, stop and report it without restoring
|
|
146
|
-
or overwriting the value. Treat residual module Git directories from a manual
|
|
147
|
-
deinit/removal as user data: block forced cleanup until they are reinitialized or
|
|
148
|
-
explicitly recovered.
|
|
75
|
+
## Use subagents when they improve throughput
|
|
149
76
|
|
|
150
|
-
|
|
77
|
+
Let the main agent own decomposition, architecture, dependencies, final gate,
|
|
78
|
+
Git closure, integration, and cleanup.
|
|
151
79
|
|
|
152
|
-
|
|
153
|
-
|
|
154
|
-
|
|
155
|
-
|
|
156
|
-
|
|
157
|
-
|
|
158
|
-
4. For one serial writer, inspect the current checkout first and work directly on
|
|
159
|
-
its current branch when it is clean. Create registered task branches/worktrees
|
|
160
|
-
only when the checkout already has changes or multiple writers run in parallel.
|
|
161
|
-
Never share one worktree between writers; parallelize only dependency-free
|
|
162
|
-
units with non-overlapping paths.
|
|
163
|
-
5. Review each stable diff with a read-only reviewer. Route blocking findings to
|
|
164
|
-
the owning fixer and re-review after any change. The main agent records the
|
|
165
|
-
current verdict with `task-review`, then hands the writer lease back before Git
|
|
166
|
-
closure when required.
|
|
167
|
-
6. After all agents have returned, the main agent executes the changed-scope fast
|
|
168
|
-
gate once, records `DEV-CLOSED`, commits, and pushes. Use `commit-push` for
|
|
169
|
-
registered isolated tasks; on a clean serial current branch, commit and push
|
|
170
|
-
that branch directly without creating a temporary branch.
|
|
171
|
-
If that configured fast gate fails only because a dependency already present
|
|
172
|
-
in the lockfile is not installed locally, restore the locked dependencies and
|
|
173
|
-
rerun that same fast gate once. Missing dependencies in an accidentally or
|
|
174
|
-
explicitly invoked standard/full diagnostic do not justify dependency
|
|
175
|
-
installation or a full-gate rerun.
|
|
176
|
-
7. For isolated tasks, the main agent runs `task-integrate` in dependency order
|
|
177
|
-
and cleans every task worktree and merged task branch. Direct serial work has
|
|
178
|
-
no temporary branch to clean.
|
|
179
|
-
8. Stop. Jenkins owns later build/deploy work and the project owner owns actual
|
|
180
|
-
acceptance. Ignore later external failures unless the user opens a diagnostic task.
|
|
80
|
+
- Run independent read-only explorer, docs, or browser questions in parallel.
|
|
81
|
+
- Dispatch fixers only for bounded, dependency-free units with non-overlapping
|
|
82
|
+
paths; give each parallel fixer its own registered worktree.
|
|
83
|
+
- Start dependent writers only after prerequisite commits are integrated.
|
|
84
|
+
- Add a reviewer only when the risk policy requires one.
|
|
85
|
+
- Do not force fan-out for small serial tasks.
|
|
181
86
|
|
|
182
|
-
|
|
87
|
+
Subagents do not commit, push, integrate, clean branches, or run the final project
|
|
88
|
+
gate. Use the bundled orchestration contract when structured assignments/results
|
|
89
|
+
are useful; ordinary main-agent work needs no task ledger.
|
|
183
90
|
|
|
184
|
-
|
|
185
|
-
and regex import rules are advisory unless the project explicitly sets
|
|
186
|
-
`structure.enforcement: blocking`. Search for reusable utilities, components,
|
|
187
|
-
clients, validation, permissions, caching, retry, and automation before adding
|
|
188
|
-
new helpers. Do not split files only to reduce line count.
|
|
91
|
+
## Run real changed-scope validation
|
|
189
92
|
|
|
190
|
-
|
|
191
|
-
|
|
93
|
+
Keep classification under `risk.rules` and executable checks under
|
|
94
|
+
`validation.routes`. Match every changed path against all routes, collect command
|
|
95
|
+
references in configuration order, remove duplicates, and run each once.
|
|
192
96
|
|
|
193
97
|
```bash
|
|
194
|
-
python3 docs/tools/autopipeline/ap.py
|
|
98
|
+
python3 docs/tools/autopipeline/ap.py validation-map-check --path <PATH>
|
|
99
|
+
python3 docs/tools/autopipeline/ap.py light-gate --scope changed --explain
|
|
195
100
|
```
|
|
196
101
|
|
|
197
|
-
|
|
198
|
-
|
|
199
|
-
|
|
200
|
-
|
|
201
|
-
|
|
202
|
-
|
|
203
|
-
-
|
|
204
|
-
|
|
205
|
-
-
|
|
206
|
-
|
|
207
|
-
- `reviewer`: correctness, security, regression, and evidence review.
|
|
208
|
-
|
|
209
|
-
For standard and high-risk write tasks, use the following fan-out/fan-in contract:
|
|
102
|
+
- Fail before staging when changed code is unmapped or a route references a
|
|
103
|
+
missing/blank command.
|
|
104
|
+
- Allow docs-only changes to use the built-in diff check.
|
|
105
|
+
- Treat `git diff --check` as additional hygiene, never as business validation.
|
|
106
|
+
- Allow focused tests and test/fix/retest loops during development.
|
|
107
|
+
- Run one final routed closure gate after the diff is stable.
|
|
108
|
+
- Do not automatically run full regression, Docker, builds, Jenkins, deployment,
|
|
109
|
+
API verification, or target checks.
|
|
110
|
+
- Do not automatically install dependencies. If the final route needs a locked
|
|
111
|
+
dependency absent from the checkout, restore it once and retry only that route.
|
|
210
112
|
|
|
211
|
-
|
|
212
|
-
role, scope, dependencies, acceptance criteria, and expected output.
|
|
213
|
-
2. Discovery roles are read-only and may run in parallel. Browser work is limited
|
|
214
|
-
to requested reproduction/evidence; it does not replace owner acceptance.
|
|
215
|
-
3. Each fixer receives `execution_mode` and owned paths. Direct mode also names
|
|
216
|
-
the clean current checkout; isolated mode supplies a task branch and absolute
|
|
217
|
-
worktree path. It may edit only its assigned checkout and must not commit,
|
|
218
|
-
push, integrate, clean, or run the project gate.
|
|
219
|
-
4. Each reviewer receives a stable diff and binds approved or changes-requested
|
|
220
|
-
to its fingerprint. Changes go back to the same fixer and invalidate approval.
|
|
221
|
-
5. Every subagent returns exactly one JSON object conforming to
|
|
222
|
-
`data/contracts/orchestration-v1.schema.json#/$defs/agentResult`, with integer
|
|
223
|
-
`contract_version: 1`. It includes node/task/role, base SHA, dependencies,
|
|
224
|
-
owned and changed paths, diff fingerprint, evidence, findings, verdict, risks,
|
|
225
|
-
and next owner. Read-only roles return no changed paths.
|
|
226
|
-
6. The main agent alone owns architecture decisions, the single fast gate per
|
|
227
|
-
write task, closure records, commits, integration, push, and branch cleanup.
|
|
113
|
+
## Keep project state small
|
|
228
114
|
|
|
229
|
-
|
|
230
|
-
|
|
231
|
-
|
|
115
|
+
Store task manifests, ownership, leases, dependencies, and review fingerprints in
|
|
116
|
+
the Git common directory. Store gate timing/evidence under `.local` by default.
|
|
117
|
+
Do not create taskbook, closure Markdown, evidence JSONL, active-task, or design
|
|
118
|
+
documents for ordinary work. Preserve existing project documents as user data;
|
|
119
|
+
create or update them only when explicitly useful.
|
|
232
120
|
|
|
233
|
-
|
|
121
|
+
Keep `docs/ENGINEERING.md` as the only manual workflow configuration source.
|
|
122
|
+
Allow direct plaintext values under `access.*`; do not invent or echo credentials.
|
|
234
123
|
|
|
235
|
-
|
|
236
|
-
- Current library/API behavior: official documentation MCP or matching skill.
|
|
237
|
-
- UI: in-app browser for local pages, Chrome for existing logged-in state,
|
|
238
|
-
Playwright for deterministic automation, Computer Use for unsupported native UI.
|
|
239
|
-
- PR/issue state: GitHub connector; local Git for local changes and pushes.
|
|
240
|
-
- Design, security, analytics, and document artifacts: use the matching installed
|
|
241
|
-
skill or connector before manual recreation.
|
|
242
|
-
- Credentials: use the direct values configured under `access.*` in
|
|
243
|
-
`docs/ENGINEERING.md`; do not invent or echo values unnecessarily.
|
|
244
|
-
|
|
245
|
-
## Optional documents and operations
|
|
124
|
+
## Install and upgrade
|
|
246
125
|
|
|
247
126
|
```bash
|
|
248
|
-
|
|
249
|
-
|
|
250
|
-
python3 docs/tools/autopipeline/ap.py
|
|
251
|
-
python3 docs/tools/autopipeline/ap.py
|
|
252
|
-
python3 docs/tools/autopipeline/ap.py
|
|
253
|
-
python3 docs/tools/autopipeline/ap.py task-status <TASK_ID>
|
|
254
|
-
python3 docs/tools/autopipeline/ap.py task-submodule-sync <TASK_ID>
|
|
255
|
-
python3 docs/tools/autopipeline/ap.py task-review <TASK_ID> --verdict <VERDICT> --diff-fingerprint <SHA256> [--reviewer <REVIEWER>]
|
|
256
|
-
python3 docs/tools/autopipeline/ap.py task-handoff <TASK_ID> --from <WRITER> --to <WRITER> [--generation <N>]
|
|
257
|
-
python3 docs/tools/autopipeline/ap.py commit-push <TASK_ID> --msg "<TASK_ID>: <summary>" [--writer <WRITER>]
|
|
258
|
-
python3 docs/tools/autopipeline/ap.py task-integrate <TASK_ID>
|
|
259
|
-
python3 docs/tools/autopipeline/ap.py task-resume <TASK_ID>
|
|
260
|
-
python3 docs/tools/autopipeline/ap.py task-finish <TASK_ID>
|
|
261
|
-
python3 docs/tools/autopipeline/ap.py task-prune
|
|
127
|
+
autocoding init
|
|
128
|
+
autocoding sync --projects .
|
|
129
|
+
python3 docs/tools/autopipeline/ap.py upgrade --dry-run
|
|
130
|
+
python3 docs/tools/autopipeline/ap.py upgrade --write
|
|
131
|
+
python3 docs/tools/autopipeline/ap.py doctor
|
|
262
132
|
```
|
|
263
133
|
|
|
264
|
-
|
|
265
|
-
|
|
134
|
+
Finish in-flight pre-4.0 registered tasks before syncing the 4.0 runtime. Upgrade
|
|
135
|
+
must preserve project configuration, access values, custom agents, optional
|
|
136
|
+
documents, and explicit model overrides while removing obsolete managed Skill
|
|
137
|
+
files and filling new managed assets.
|