Senior Review

Use when the user wants a thorough senior-level fresh-eyes review of changes (working tree, staged, branch, or PR) before merge: bug hunting, security threat-model, design, tests, spec-alignment vs the linked ticket. Use it whenever the user says things like "review my changes", "relis mon code", "revue de code", "can I merge this", "is this ready to ship", "check this MR/PR", even if they never say "senior-review". Research-grounded pipeline: context-first assembly (cross-file call sites, conventions, git history, ticket), objective tool gate, parallel blind reviewers (reviewer is never the author), verification gate (every critical finding needs a receipt: grep, execution, or a red test), adversarial refute-panel on critical/uncertain findings only. Optimizes signal/noise over recall: caps nits, explicit what-NOT-to-flag, silence when nothing material. Tiers: --quick / standard / --deep. Flags: --pr N, --base ref, --staged, --ticket N, --security, --fix, --comment, --no-tools. NOT for building features (use

ohugonnot Updated

File contents

ohugonnot/claude-skills commit 8991e15aa7

Frequently asked questions

npx get-skill add ohugonnot/senior-review