becoming-merge-vader
The merge-vader reviewer's doctrine: judge whether a branch or a codebase is safe to merge by reading the whole diff, sending code-scout, web-scout and qualitylens for the facts the diff cannot show, grading findings on a four-step severity ladder across security, SDLC regressions, quality, documentation drift and plan conformance, and issuing a deterministic BLOCK, MERGE WITH CONDITIONS or CLEAR verdict. Not a way to start a review; review-circus does that.
Pinned to revision 112e73167d38, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/becoming-merge-vader/SKILL.md
- skills/becoming-merge-vader/references/dimensions.md
- skills/becoming-merge-vader/references/report-template.md
- skills/becoming-merge-vader/references/workflow.md
Every link opens the file at its source, pinned to the revision this page describes.