@elvis1513/auto-coding-skill 4.0.0 → 4.1.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 +38 -9
- package/cli/assets/agents/reviewer.toml +3 -2
- package/cli/assets/skill/SKILL.md +45 -16
- package/cli/assets/skill/data/policies/workflow-migrations-v1.json +291 -5
- package/cli/assets/skill/data/templates/ENGINEERING.md +46 -19
- package/cli/assets/skill/data/templates/bridges/AGENTS.md +133 -27
- package/cli/assets/skill/scripts/ap.py +241 -50
- package/cli/assets/skill/scripts/scaffold_templates.py +40 -5
- package/cli/src/index.js +172 -85
- package/cli/tests/ap_concurrency_test.py +62 -10
- package/cli/tests/ap_profiles_test.py +27 -20
- package/cli/tests/index.test.js +78 -62
- package/package.json +1 -1
- package/cli/assets/skill/data/templates/docs/tasks/closure-log.md +0 -17
- package/cli/assets/skill/data/templates/docs/tasks/taskbook.md +0 -30
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
workflow:
|
|
3
|
-
skill_version: "4.
|
|
3
|
+
skill_version: "4.1.0"
|
|
4
4
|
mode: "dev"
|
|
5
5
|
profile: "auto"
|
|
6
6
|
completion: "push"
|
|
@@ -50,17 +50,16 @@ concurrency:
|
|
|
50
50
|
disposable_ignored: []
|
|
51
51
|
|
|
52
52
|
commands:
|
|
53
|
-
#
|
|
54
|
-
#
|
|
53
|
+
# Optional convenience command. Projects may instead define only the named
|
|
54
|
+
# commands referenced by validation.routes. `autocoding sync` fills this only
|
|
55
|
+
# when package.json declares `test:changed`.
|
|
55
56
|
project_fast: ""
|
|
56
57
|
|
|
57
58
|
validation:
|
|
58
59
|
on_unmapped: "error"
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
exclude: ["*.md", "docs/**"]
|
|
63
|
-
commands: ["project_fast"]
|
|
60
|
+
# Initialization must replace this with explicit project path-to-command
|
|
61
|
+
# mappings. An empty list is intentionally fail-closed for code changes.
|
|
62
|
+
routes: []
|
|
64
63
|
|
|
65
64
|
risk:
|
|
66
65
|
rules: []
|
|
@@ -80,6 +79,7 @@ optimization:
|
|
|
80
79
|
report_accepted_debt_as_findings: false
|
|
81
80
|
|
|
82
81
|
docs:
|
|
82
|
+
framework: "engineering-centered"
|
|
83
83
|
design_dir: "docs/design"
|
|
84
84
|
health_baseline: "docs/reviews/project-health-baseline.md"
|
|
85
85
|
optimization_backlog: "docs/reviews/optimization-backlog.md"
|
|
@@ -91,7 +91,7 @@ docs:
|
|
|
91
91
|
|
|
92
92
|
# Engineering Workflow
|
|
93
93
|
|
|
94
|
-
<!-- auto-coding-skill:managed-workflow:start version=4.
|
|
94
|
+
<!-- auto-coding-skill:managed-workflow:start version=4.1.0 -->
|
|
95
95
|
|
|
96
96
|
This file contains project facts and the small amount of configuration the
|
|
97
97
|
generic workflow cannot infer. Normal delivery is:
|
|
@@ -99,8 +99,16 @@ generic workflow cannot infer. Normal delivery is:
|
|
|
99
99
|
`analysis → decomposition → necessary design → development → one final fast
|
|
100
100
|
changed-scope gate → commit/push`.
|
|
101
101
|
|
|
102
|
-
Target-branch push ends
|
|
103
|
-
|
|
102
|
+
Target-branch push ends normal coding. Jenkins, deployment, and owner acceptance
|
|
103
|
+
happen later. When the user explicitly asks to diagnose a failure caused by the
|
|
104
|
+
pushed change, diagnosis and repair may continue in the same conversation and
|
|
105
|
+
task scope without creating another taskbook/lifecycle entry.
|
|
106
|
+
|
|
107
|
+
The Skill is a selectable set of guardrails, not a requirement to execute every
|
|
108
|
+
command on every task. Read-only work, obvious clean-checkout changes, and pure
|
|
109
|
+
ledger/archive reconciliation normally skip classify, task-start, durable design,
|
|
110
|
+
reviewer, and subagents. Use each mechanism only when its expected quality or
|
|
111
|
+
throughput benefit is greater than its coordination cost.
|
|
104
112
|
|
|
105
113
|
## Delivery levels
|
|
106
114
|
|
|
@@ -127,8 +135,8 @@ python3 docs/tools/autopipeline/ap.py classify --scope auto \
|
|
|
127
135
|
- A clean checkout with one writer uses the current branch directly.
|
|
128
136
|
- A checkout that already contains unrelated changes uses an isolated task
|
|
129
137
|
branch/worktree.
|
|
130
|
-
- Two or more concurrent writers always use separate worktrees with
|
|
131
|
-
non-overlapping owned paths.
|
|
138
|
+
- Two or more concurrent writers always use separate task IDs/worktrees with
|
|
139
|
+
non-overlapping owned paths; each `task-start` creates exactly one writer lease.
|
|
132
140
|
- A task that produces no diff creates no commit or push; direct mode creates no
|
|
133
141
|
temporary branch at all.
|
|
134
142
|
- Never restore, reset, stash, clean, or otherwise modify unknown user or task
|
|
@@ -185,9 +193,9 @@ python3 docs/tools/autopipeline/ap.py validation-map-check --tracked
|
|
|
185
193
|
|
|
186
194
|
Focused tests may be run and rerun during implementation. The "one gate" rule
|
|
187
195
|
means one final routed closure gate after the diff is stable; it does not prohibit
|
|
188
|
-
reasonable test/fix/retest cycles. Do not install dependencies
|
|
189
|
-
|
|
190
|
-
|
|
196
|
+
reasonable test/fix/retest cycles. Do not install dependencies proactively. Only
|
|
197
|
+
after the selected final route fails because a repository-locked dependency is
|
|
198
|
+
absent may it be restored once; then retry only that affected route.
|
|
191
199
|
|
|
192
200
|
## Design, review, and subagents
|
|
193
201
|
|
|
@@ -204,7 +212,19 @@ restore the locked dependency once and retry that same command only.
|
|
|
204
212
|
- The main agent alone owns the final gate, commit, push, ordered integration,
|
|
205
213
|
and temporary-branch cleanup.
|
|
206
214
|
|
|
207
|
-
##
|
|
215
|
+
## Documentation framework and lightweight records
|
|
216
|
+
|
|
217
|
+
This managed block and the installed Skill define the shared workflow. Content
|
|
218
|
+
outside this block may describe project facts only: product/domain boundaries,
|
|
219
|
+
repository ownership, runtime/deployment topology, external-system safety,
|
|
220
|
+
validation commands, and links to current contracts/decisions. It must not
|
|
221
|
+
duplicate delivery levels, agent roles, task lifecycle, gate semantics, or
|
|
222
|
+
completion rules.
|
|
223
|
+
|
|
224
|
+
When project facts are too large for this file, scaffold `docs/project/` and link
|
|
225
|
+
those documents here. Code, tests, schemas, migrations, and runtime configuration
|
|
226
|
+
remain authoritative for behavior that exists now; historical records never
|
|
227
|
+
override them.
|
|
208
228
|
|
|
209
229
|
Ordinary tasks do not create taskbook, closure Markdown, evidence JSONL, or active
|
|
210
230
|
task documents. Isolated-task coordination state lives under the Git common
|
|
@@ -213,6 +233,11 @@ ledgers are user data: upgrades preserve them but do not require or update them.
|
|
|
213
233
|
Use `record-closure`, documentation scaffolds, or a baseline only when the user or
|
|
214
234
|
task genuinely needs a durable artifact.
|
|
215
235
|
|
|
236
|
+
Pure taskbook, closure, archive, or ledger consistency work is a terminal
|
|
237
|
+
maintenance action. Validate the affected documents and commit once; do not
|
|
238
|
+
create a new active task, review cycle, closure record, or evidence chain for the
|
|
239
|
+
act of closing the previous record.
|
|
240
|
+
|
|
216
241
|
Historical debt does not block product work. Block only new or worsened P0/P1
|
|
217
242
|
issues; keep accepted debt in an optional backlog and address it through explicit
|
|
218
243
|
governance tasks.
|
|
@@ -224,7 +249,9 @@ initialization. Direct plaintext values are allowed. The generic workflow neithe
|
|
|
224
249
|
forbids them nor rewrites a project's credential policy.
|
|
225
250
|
|
|
226
251
|
Full regression, structure scans, Docker, Jenkins, API checks, target verification,
|
|
227
|
-
and deployment remain explicit diagnostic commands. Do not run
|
|
228
|
-
|
|
252
|
+
and deployment remain explicit diagnostic commands. Do not run or poll them
|
|
253
|
+
during normal closure. An explicitly requested diagnosis of a failure caused by
|
|
254
|
+
the just-pushed change may stay in the same conversation/task; it does not require
|
|
255
|
+
an artificial second lifecycle record.
|
|
229
256
|
|
|
230
257
|
<!-- auto-coding-skill:managed-workflow:end -->
|
|
@@ -1,29 +1,135 @@
|
|
|
1
|
-
<!-- auto-coding-skill:managed-agents:start version=4.
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
1
|
+
<!-- auto-coding-skill:managed-agents:start version=4.1.0 -->
|
|
2
|
+
|
|
3
|
+
# Repository Delivery Rules
|
|
4
|
+
|
|
5
|
+
This file is fully managed by `auto-coding-skill`. Keep project-specific facts,
|
|
6
|
+
commands, access values, path mappings, architecture boundaries, and runtime
|
|
7
|
+
notes in `docs/ENGINEERING.md` or its linked project documents. Do not add local
|
|
8
|
+
workflow rules here; the next Skill sync replaces this file as a whole.
|
|
9
|
+
|
|
10
|
+
## Required sources
|
|
11
|
+
|
|
12
|
+
Before changing a repository, read:
|
|
13
|
+
|
|
14
|
+
1. the current user request;
|
|
15
|
+
2. this file;
|
|
16
|
+
3. `docs/ENGINEERING.md` frontmatter and project-specific sections;
|
|
17
|
+
4. only the source, tests, contracts, migrations, runtime configuration, or
|
|
18
|
+
decision records relevant to the requested scope.
|
|
19
|
+
|
|
20
|
+
Use this authority order when sources disagree:
|
|
21
|
+
|
|
22
|
+
1. the current user request;
|
|
23
|
+
2. executable code, tests, schemas, migrations, and runtime configuration for
|
|
24
|
+
behavior that exists now;
|
|
25
|
+
3. `docs/ENGINEERING.md` for project boundaries, access, risk, and validation;
|
|
26
|
+
4. interface documentation for intended external contracts;
|
|
27
|
+
5. accepted DD/ADR documents for lasting decisions;
|
|
28
|
+
6. taskbooks, closure logs, summaries, reviews, and deployment records as
|
|
29
|
+
historical evidence only.
|
|
30
|
+
|
|
31
|
+
Do not let stale historical documents override current implementation. If a
|
|
32
|
+
requested change intentionally changes a contract or decision, update the
|
|
33
|
+
authoritative documentation in the same change.
|
|
34
|
+
|
|
35
|
+
## Delivery flow
|
|
36
|
+
|
|
37
|
+
This Skill is a selectable guardrail, not a mandatory ceremony. The model first
|
|
38
|
+
decides which mechanisms have positive net value for the current task. Read-only
|
|
39
|
+
work, an obvious clean-checkout edit, or terminal ledger reconciliation normally
|
|
40
|
+
needs no classify command, task lifecycle, design record, reviewer, or subagent.
|
|
41
|
+
Use the smallest safe path for repository changes:
|
|
42
|
+
|
|
43
|
+
`analysis → decomposition → necessary design → development → one final
|
|
44
|
+
changed-scope gate → commit/push`.
|
|
45
|
+
|
|
46
|
+
- Analyze impact and reuse points before writing.
|
|
47
|
+
- Split only genuinely independent work; keep dependencies and file ownership
|
|
48
|
+
explicit.
|
|
49
|
+
- Create DD/ADR only for lasting cross-module, API, data, security, deployment,
|
|
50
|
+
or key user-flow decisions.
|
|
51
|
+
- Focused tests may run and rerun during implementation. Run the configured final
|
|
52
|
+
routed gate once after the diff is stable.
|
|
53
|
+
- Commit and push all intended changes. A successful target-branch push ends
|
|
54
|
+
normal coding work.
|
|
55
|
+
- Do not poll Jenkins, deploy, or perform target acceptance automatically. If the
|
|
56
|
+
user explicitly asks to diagnose a failure caused by the pushed change, keep
|
|
57
|
+
that diagnosis and fix in the same conversation and task scope without
|
|
58
|
+
creating an artificial new ledger task.
|
|
59
|
+
|
|
60
|
+
## Git safety and parallel work
|
|
61
|
+
|
|
62
|
+
Inspect the checkout before writing.
|
|
63
|
+
|
|
64
|
+
- One writer in a clean checkout works on the current branch.
|
|
65
|
+
- Pre-existing unrelated changes, an already active writer, or two or more
|
|
66
|
+
writers require isolated task branches/worktrees.
|
|
67
|
+
- Each parallel writer gets one registered worktree, non-overlapping
|
|
68
|
+
`owned_paths`, dependency commit SHAs, a distinct task ID, and a writer lease.
|
|
69
|
+
- Never let multiple writing agents share a checkout.
|
|
70
|
+
- Never restore, reset, stash, clean, overwrite, or commit unknown changes.
|
|
71
|
+
- If a task produces no diff, create no commit or push. Direct work creates no
|
|
72
|
+
temporary branch.
|
|
73
|
+
- The main agent alone integrates by dependency order, pushes the target branch,
|
|
74
|
+
and removes only clean, safely merged temporary worktrees and branches.
|
|
75
|
+
|
|
76
|
+
Do not upgrade or sync the Skill while any registered task is active. Finish,
|
|
77
|
+
integrate, or clean it with the installed runtime first so lifecycle semantics do
|
|
78
|
+
not change mid-task.
|
|
79
|
+
|
|
80
|
+
## Risk, agents, and review
|
|
81
|
+
|
|
82
|
+
- Micro and standard tasks default to the main agent. Do not require design,
|
|
83
|
+
fan-out, a task ledger, or a reviewer merely because a change is non-trivial.
|
|
84
|
+
- Use read-only explorer, documentation researcher, or browser roles only for
|
|
85
|
+
independent questions whose expected value exceeds coordination cost.
|
|
86
|
+
- Use parallel fixers only for bounded, dependency-aware units with separate
|
|
87
|
+
worktrees and non-overlapping paths.
|
|
88
|
+
- Require independent review for high-risk, cross-module, parallel integration,
|
|
89
|
+
or explicitly configured work.
|
|
90
|
+
- Review blocks only defects introduced or worsened inside the promised task
|
|
91
|
+
scope. Record adjacent pre-existing issues as non-blocking follow-ups.
|
|
92
|
+
- Any semantic code/config change invalidates review approval and requires a new
|
|
93
|
+
diff fingerprint. A mechanical documentation-only correction may receive a
|
|
94
|
+
targeted recheck by the same reviewer against the new fingerprint.
|
|
95
|
+
- Historical debt does not block ordinary delivery. Block only new or worsened
|
|
96
|
+
P0/P1 issues; handle broad cleanup through an explicit governance task.
|
|
97
|
+
|
|
98
|
+
## Validation
|
|
99
|
+
|
|
100
|
+
`risk.rules` controls reasoning and review depth. `validation.routes` controls
|
|
101
|
+
executable checks. Keep them separate.
|
|
102
|
+
|
|
103
|
+
- Every changed code/config path must match one or more explicit validation
|
|
104
|
+
routes in `docs/ENGINEERING.md`.
|
|
105
|
+
- Run every matched command once in stable configuration order and de-duplicate
|
|
106
|
+
repeated command references.
|
|
107
|
+
- Unmapped code or a missing/blank command fails before staging.
|
|
108
|
+
- Documentation-only work may use the built-in diff/format check.
|
|
109
|
+
- `git diff --check` is additional hygiene and never business-code validation.
|
|
110
|
+
- Use project-native fast checks. Do not automatically run a full repository
|
|
111
|
+
build, Docker, Jenkins, deployment, live-device writes, or target validation.
|
|
112
|
+
- Do not install dependencies proactively. Only after the selected final route
|
|
113
|
+
fails because a repository-locked dependency is absent may it be restored once;
|
|
114
|
+
then retry only that affected route.
|
|
115
|
+
- External-system or real-device writes require the project's explicit safety
|
|
116
|
+
rule or user confirmation; prefer fixtures/simulators for repeatable local
|
|
117
|
+
coverage where the project supplies them.
|
|
118
|
+
|
|
119
|
+
## Documentation and access
|
|
120
|
+
|
|
121
|
+
- `docs/ENGINEERING.md` is the single project workflow configuration source. Its
|
|
122
|
+
managed block explains the shared protocol; content outside that block contains
|
|
123
|
+
project facts, not competing workflow instructions.
|
|
124
|
+
- Put durable product/domain facts, repository maps, and runtime/deployment facts
|
|
125
|
+
in `docs/project/` when they are too large for `ENGINEERING.md`.
|
|
126
|
+
- Ordinary work does not create taskbook, closure Markdown, evidence JSONL,
|
|
127
|
+
active-task documents, or design files. Pure ledger/archive reconciliation is
|
|
128
|
+
a terminal maintenance action and must not create another task lifecycle.
|
|
129
|
+
- Generated task state, leases, fingerprints, and gate evidence stay in Git
|
|
130
|
+
common/local state so recording them cannot change the reviewed diff.
|
|
131
|
+
- Fill the configured project/Jenkins/GitLab/Nexus access fields during project
|
|
132
|
+
initialization. Plaintext values are allowed by the generic workflow; do not
|
|
133
|
+
invent or echo credentials unnecessarily.
|
|
28
134
|
|
|
29
135
|
<!-- auto-coding-skill:managed-agents:end -->
|