Claude Skills by norton77930

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

A relentless interview to sharpen a plan or design.

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating spec/plan asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants a standards-vs-spec review of a branch or work-in-progress changes, or asks to "review since X".

Use before claiming any work is complete, fixed, done, or passing — run the most relevant verification first and report evidence rather than assumptions.