القائمة
Check changed feature code against charter architecture rules: layering, cycles, forbidden patterns, names, and size.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Analyze changed code for complex, under-tested functions using CRAP scoring; produce ranked refactor and test recommendations.
Validate strict DAE quality gates after implementation-affecting changes, require machine-readable evidence, and write the quality-gate summary before completion or release.
This skill should be used when the user asks to "run mutation testing", "mutate my code", "kill mutants", "check test quality", "find surviving mutants", "verify test effectiveness with mutations", "run stryker", "run mutmut", "run pitest", "set up mutation testing", "how good are my tests", "are my tests catching bugs", or mentions mutation testing, mutation score, or mutant survival in the context of testing. It adds a third validation layer to the ATDD workflow: after acceptance tests verify WHAT and unit tests verify HOW, mutation testing verifies that tests actually catch bugs.
This skill should be used when the user asks to "build a feature", "implement a feature", "add functionality", "start development", "write acceptance tests", "write specs", "use ATDD", "use TDD with acceptance tests", or begins any feature implementation work. Also available as the atdd plugin's main skill. Enforces the Acceptance Test Driven Development workflow: write Given/When/Then specs before code, generate a project-specific test pipeline, and maintain two test streams.
This skill should be used when the user asks to "build a feature with a team", "use ATDD with agents", "create an ATDD team", "set up a team for ATDD", "orchestrate agents for ATDD", "use team-based development", "coordinate agents for feature development", "run the ATDD workflow with teammates", "add ATDD to my team", "extend my team with ATDD", "join the team with ATDD agents", "add spec-writer and reviewer to the team", or "add ATDD roles to the existing team". It orchestrates a six-phase ATDD workflow — spec writing, spec review, pipeline generation, implementation, refine, verify & harden — spawning a fresh agent per phase so no agent erodes across a long-running feature.
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
| name | arch-check |
| description | Check changed feature code against charter architecture rules: layering, cycles, forbidden patterns, names, and size. |
Run the charter architecture fitness check — Checkpoint 7 (Light Verify),
alongside crap-analyzer. Turns the charter's architectural vision from prose
into an objective gate: dae_arch.py reads the manifest's architecture: rules
and reports violations.
Read-only on the codebase — it reports, it does not fix.
Checkpoint 7, after the feature's code is implemented and refined. Also useful
as a standalone audit (--full) of an existing project.
Not for: change-risk analysis (crap-analyzer); artifact consistency
(consistency-check); fixing violations (that is a human/agent decision per
violation).
Verify the prior checkpoint is complete: run
${PLUGIN_ROOT}/scripts/dae_handoff.py <feature-dir> --through 6. On a
non-zero exit, stop and surface the gap to the human.
Verify branch hygiene: run ${PLUGIN_ROOT}/scripts/dae_branch.py <feature-dir>.
On a non-zero exit, stop and surface the message to the human — switch
branches and re-invoke. The check honors the git.manual: true manifest
opt-out.
After the gate passes, show the pipeline breadcrumb: run
${PLUGIN_ROOT}/scripts/dae_progress.py <feature-dir> and present its
output to the human — it shows where this checkpoint sits in the DAE pipeline.
The breadcrumb is advisory: a non-zero exit or a missing progress.md never
blocks the skill. Then create one Codex plan item per workflow step below. See
${PLUGIN_ROOT}/references/progress-indicator.md.
Run ${PLUGIN_ROOT}/scripts/dae_arch.py <methodology-root> (add --full
for a whole-project audit). If it reports "no architecture: section", tell the
user the charter has no machine-readable architecture rules yet and stop.
Group the violations by kind (layering first — it is the architectural-vision
core). For each, show file:line and the rule. Do not auto-fix.
For each violation, the human decides: a real break (fix the code), or a rule
that no longer fits (amend manifest.architecture — and the charter prose).
dae_arch.py exiting non-zero means Checkpoint 7's architecture-fitness exit
criterion is unmet until the violations are resolved.
Emit a summary per ${PLUGIN_ROOT}/references/handoff-summary.md.
checkpoint: 7; the exit_criteria block asserts the architecture-fitness
criterion with verified_by: tool and the dae_arch.py exit status as evidence.
architecture: manifest section (§2); the Checkpoint Exit Contract (§8)