change-review

Summary

Use this skill for structured pre-merge review. The default stance is blocker-first and risk-first, with concrete fixes included when they are clear and high confidence.

When to use

• A PR, patch, or local diff needs structured review before merge.
• A change spans multiple layers and benefits from independent specialist perspectives.
• The team wants a synthesized findings list rather than raw reviewer commentary.
• The diff is large enough that parallel inspection is more efficient than one sequential pass.

When not to use

• The user only wants a compile check or a short diff summary.
• The task is to implement or fix code rather than review it.
• The change is trivial enough that multi-agent review would add more noise than signal.
• The user wants a purely stylistic pass with no concern for correctness, risk, or regressions.

Inputs