菜单
Repair every reported architecture violation with partitioned subagent work and rerun boundary feedback until green. TRIGGER when: architecture lint reports violations or an operator asks to fix dependency direction, purity, composition-root, or cycle problems.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run the complete Contree arc from idea to independently reviewed working software without routine operator phase transitions: change sets the contract, sync audits it, tdd closes every gap, mutation and completion sync prove the result, and second-opinion findings are repaired before completion. TRIGGER when: the user wants the full workflow, asks to take an idea through implementation, asks to make the project complete, or wants change/sync/tdd handled end to end.
Set up fast test feedback for coding agents by configuring normal, journey, and impacted-test commands plus project save hooks. TRIGGER when: an operator asks to configure a test framework, test commands, test output, changed-test selection, test hooks, or Docker-backed tests.
Comprehensively install Contree's coding-agent feedback loops through a dynamic, operator-guided workflow. TRIGGER when: the operator asks for full, complete, comprehensive, or luxury Contree setup, or starts a project and wants all steering configured.
Set up fast conventional code linting, automatic repair, CI enforcement, and synchronous coding-agent feedback. TRIGGER when: an operator asks to add, configure, improve, or fix linting or code-quality feedback.
Set up test trees and durable project-local coding-agent steering without implementing tests. TRIGGER when: an operator asks to establish, discover, backfill, configure, or set up test trees for an existing or new project.
Set up and prove fast mutation-test feedback, then strengthen Domain and Use-case tests until the agreed threshold passes. TRIGGER when: an operator asks to configure, run, optimize, or fix mutation testing.
| name | fix-architecture |
| description | Repair every reported architecture violation with partitioned subagent work and rerun boundary feedback until green. TRIGGER when: architecture lint reports violations or an operator asks to fix dependency direction, purity, composition-root, or cycle problems. |
Repair architecture violations at their source without weakening the architecture feedback.
Read MENTAL_MODEL.md, the architecture-linter configuration, the relevant source, and tests. Run the project's architecture command first and preserve its complete output. Group violations by the boundary crossed and the source files that must change.
If a violation conflicts with the operator's intended architecture or MENTAL_MODEL.md, explain the concrete conflict and resolve the decision with the operator before changing the enforced boundary. Ordinary implementation violations do not require operator input.
Partition all reported violations into complete, non-overlapping work for subagents. Give each subagent:
Run independent partitions concurrently. Keep shared composition roots, public port types, architecture configuration, and cross-partition reconciliation with the coding agent so subagents do not overlap.
Subagents fix the production design and preserve observable behavior. Do not disable rules, weaken boundaries, add exemptions, introduce ignore directives, move forbidden work behind aliases, or delete behavior to make lint green.
Reconcile every subagent change at shared seams. Resolve duplicate ports, incompatible moved types, composition-root wiring, and test coverage yourself. Run the affected normal tests, then rerun the complete architecture command so every architecture rule executes together.
If violations remain, Repartition every remaining violation into fresh non-overlapping subagent work. Reconcile and rerun again until architecture lint passes. Repeated appearances of the same rule are unresolved work, not a reason to suppress the rule.
Do not report completion while any violation remains. Finish only when the complete architecture command and affected tests pass, with no disabled rule, weakened boundary, or exemption in the change.
