@elvis1513/auto-coding-skill 3.0.4 → 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 +159 -328
- package/cli/assets/agents/explorer.toml +1 -1
- package/cli/assets/agents/fixer.toml +4 -4
- package/cli/assets/agents/reviewer.toml +12 -12
- package/cli/assets/skill/SKILL.md +135 -234
- package/cli/assets/skill/data/policies/workflow-migrations-v1.json +291 -5
- package/cli/assets/skill/data/templates/ENGINEERING.md +164 -292
- package/cli/assets/skill/data/templates/bridges/AGENTS.md +133 -14
- package/cli/assets/skill/scripts/ap.py +884 -221
- package/cli/assets/skill/scripts/scaffold_templates.py +40 -5
- package/cli/src/index.js +180 -93
- package/cli/tests/ap_concurrency_test.py +109 -24
- package/cli/tests/ap_profiles_test.py +81 -41
- package/cli/tests/index.test.js +114 -77
- package/package.json +2 -2
- 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,16 +1,135 @@
|
|
|
1
|
-
<!-- auto-coding-skill:managed-agents:start version=
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
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.
|
|
15
134
|
|
|
16
135
|
<!-- auto-coding-skill:managed-agents:end -->
|