sdlc-review

Dispatch this Skill after the execution stage finishes. It establishes the change-set with git diff, sweeps ten failure-mode categories, and returns cited findings as one JSON block while appending the round to review.md.

It checks verification gaps, cross-reference ripples, pre-existing versus new regressions, missing edge cases, ordering and concurrency hazards, resource cleanup gaps, backward-compatibility breaks, safety regressions, efficiency regressions, and implicit-contract assumptions.

Yes. The deliverable under review may be source code, a generated report, a workflow configuration, a data pipeline definition, or a written procedure. Findings use section names, step numbers, or field paths as locators when no line numbering exists.

No. It is strictly read-only toward the material under review and returns findings as text. The only file it writes is its own findings record in review.md, preserving the maintainer's ability to judge each fix.

Pre-existing defects stay in the findings list with preExisting set to true, separating them from release-blocking regressions the change introduced. The change-set is established first via git diff so authorship is never guessed.

On a non-git target or clean tree, the reviewer states this in its notes and marks findings preExisting false only where the named material itself shows the defect, rather than guessing at authorship.