Loading...
Loading...
Found 46 Skills
Use red-green-refactor to implement features and bug fixes with tests first. Only use if requested explicitely, for general tdd use mattpocock/skills/tdd
Observe Before Editing
Systematic 4-phase debugging: understand the failure, form hypotheses, test one change at a time, fix with confidence. Activate when tests fail unexpectedly, errors occur, behavior is wrong, or something that worked before is now broken. Triggers on: "debug", "why is this failing", "test failure", "unexpected error", "bug", "broken".
Use when RLM requirement involves debugging a bug, test failure, or unexpected behavior. Insert Phase 1.5 between Phase 1 and Phase 2 to perform systematic root cause analysis before attempting any fixes.
Used when implementing any feature or bug fix before writing production code
Use when a program crashes, a test fails, or code produces wrong results and reading the source isn't enough to see why. Lets you pause execution at any line and inspect the actual runtime state, variable values, types, call stacks, to find what went wrong.
Investigate, fix, postmortem, prevent. Full incident lifecycle from bug report to systemic prevention. Use when: production down, critical bug, incident response, post-incident review. Composes: /investigate, /fix, /postmortem, /codify-learning.
Diagnose and fix errors with Codex delegation. Traces error to root cause, researches approach, delegates fix, verifies. Use when: bug reports, error messages, stack traces, test failures.
Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.
Root cause analysis and debugging protocols. Use when encountering errors, test failures, unexpected behavior, stack traces, or when code behaves differently than expected.
Investigate suspected bugs with git archaeology and root cause analysis. Triggers: "bug", "broken", "doesn't work", "failing", "investigate bug".
Bug diagnosis and fixing specialist - analyzes errors, identifies root causes, provides fixes, and writes regression tests