Review code

Decide whether a change fulfills its intent and is safe to merge. Give the author evidence-backed findings, the questions that could change that decision, and an honest account of coverage.

What this skill adds

A manual prompt or built-in review can draw on the same code-review abilities. This skill supplies a standing review contract:

• Review the promised outcome, including omissions in unchanged code.
• Follow consequences beyond changed lines and challenge both suspected defects and consequential assumptions behind approval.
• Preserve findings and unresolved questions across fixes.
• Return a pinned, validated record that a person can inspect and publishing skills can consume.

Use your judgment to choose the investigation, tools, depth, and proof strategy. Spend effort where a wrong conclusion would matter. The contract defines what the review must establish; it does not prescribe a search sequence or a fixed checklist of bug patterns.

Inputs