scrutinize

Outsider-perspective end-to-end review of a plan, PR, or code change. First questions intent and whether a simpler/more elegant approach would achieve the same goal, then traces the actual code path (not just the diff) to verify the change does what it claims. Output is concise, actionable, and every call carries its rationale. Trigger on /scrutinize and proactively whenever the user asks to review, audit, sanity-check, or get a second opinion on a plan, PR, diff, design doc, or proposed code change.

Try your first task

Sanity-check a proposed code change

Start a fresh conversation. Replace the highlighted placeholders.

Use the scrutinize skill to review [PR, diff, plan, or design-document path] in the codebase at [absolute repository path]. The intended goal is [one-sentence goal]. Question whether a simpler change would achieve it, trace the affected behavior through the real code path, and return concise severity-ordered findings with rationale, evidence, a minimal suggested change, and a one-line verdict. Do not publish the review.

Required inputs

Absolute repository path
PR, diff, plan, or design-document location
One-sentence intended goal

Suggested template by Skill Leaderboard, grounded in the linked source. Task evidence ↗

Inside SKILL.md

65 lines

Section content has not been verified for this skill yet.

Full source remains withheld under the current source-display policy. Read the author’s source ↗