| name | archi-diff |
| description | Review current changes for architecture risk, boundary pressure, coupling, duplication, and maintainability impact. |
Archi Diff
Use this skill for change-scoped architecture review.
Workflow
- Inspect the available architecture-analysis command shape before assuming
flags.
- Use
archi-evidence-map first when the evidence source is unclear or when
tools are unavailable.
- Run or read incremental architecture review evidence only when available or
requested.
- Read changed source files and nearby ownership boundaries directly.
- Use vendored
code-review-and-quality when the diff needs broad quality
coverage beyond architecture-only findings.
- Use vendored
requesting-code-review when the user wants an independent
review lane or review handoff.
- Read
.architec/architec-summary.md first when present.
- Use
.architec/architec-analysis.json for exact scores, concerns, signals,
hotspots, and artifact paths.
- Focus on changed-component concerns, boundary pressure, duplication,
hotspots, and recommendations.
Output
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.
