Menu
Review current changes for architecture risk, boundary pressure, coupling, duplication, and maintainability impact.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Fix bugs by reproducing the failure first, making the smallest correction, and proving the regression is covered. Use for bug reports, failing tests, and regressions.
Fix failing tests or CI by reading logs, identifying the smallest failing surface, making a minimal change, and rerunning targeted verification. Use when given CI logs, failing commands, or broken checks.
Scan relevant source, tests, commands, and existing project patterns before editing code. Use before non-trivial implementation, bug fixing, or refactoring when the right local pattern is unclear.
Control error handling, defaults, retries, compatibility paths, and fallback behavior. Use before adding catch blocks, defaults, shims, optional values, retries, or graceful degradation.
Prevent large-file growth and mixed-responsibility edits. Use when adding significant logic to a large file, mixed-purpose module, or file with repeated conditionals.
Implement the smallest safe repo-native code change for the requested behavior. Use for feature work, small refactors, and multi-file implementation tasks.
| name | archi-diff |
| description | Review current changes for architecture risk, boundary pressure, coupling, duplication, and maintainability impact. |
Use this skill for change-scoped architecture review.
archi-evidence-map first when the evidence source is unclear or when
tools are unavailable.code-review-and-quality when the diff needs broad quality
coverage beyond architecture-only findings.requesting-code-review when the user wants an independent
review lane or review handoff..architec/architec-summary.md first when present..architec/architec-analysis.json for exact scores, concerns, signals,
hotspots, and artifact paths.Lead with the verdict:
Verdict
- diff status:
- incremental score:
Blocking Issues
- ...
Impacted Areas
- ...
Required Changes
- ...
Do not paste raw JSON. Use direct code references for findings that need engineering action.
If no architecture-analysis tool is available, continue with direct diff and source review, and state the missing evidence as residual risk.