Loading...
Loading...
Found 5 Skills
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Plain-language fix guide for failing GTM tests. Use when tests have failed and the developer needs step-by-step instructions to fix each issue. Reads gtm-test-results.json and writes a fix guide in plain English - no GTM expertise required to follow. No API calls. Trigger on - "fix guide", "how do I fix failing tests", "tests failing", "gtm test failures", "fix my tracking", "what broke".
Systematic methodology for debugging bugs, test failures, and unexpected behavior. Use when encountering any technical issue before proposing fixes. Covers root cause investigation, pattern analysis, hypothesis testing, and fix implementation. Use ESPECIALLY when under time pressure, "just one quick fix" seems obvious, or you've already tried multiple fixes. NOT for exploratory code reading.
Build verification, error recovery, and application of review fixes. Use this when the user mentions build verification, error recovery, applying review fixes, test failures, lint errors, or CI breaks. Do NOT load this for: implementation work, reviews, setup, or new feature development.
Auto-detects your test framework, runs the full suite, diagnoses failures, and fixes them. Use after making code changes to verify tests pass, or when you encounter test failures you want diagnosed and fixed automatically.