Loading...
Loading...
Found 52 Skills
Use when encountering bugs, unexpected behavior, test failures, or errors during development. Enforces a rigorous 4-phase investigation process that prevents shotgun debugging. Triggers: test failure, runtime error, unexpected behavior, production incident, performance regression.
Use this whenever you encounter any bugs, test failures, or abnormal behavior, and execute it before proposing a fix
Use when debugging bugs, test failures, build failures, performance regressions, or unexpected behavior and you need root-cause investigation before proposing fixes. Trigger on requests to debug, investigate why something broke, or find the source of a technical issue.
Four-phase debugging framework with root cause tracing - understand the source before proposing fixes. Use when investigating bugs, errors, unexpected behavior, or failed tests.
Four-phase debugging methodology with root cause analysis. Use when investigating bugs, fixing test failures, or troubleshooting unexpected behavior. Emphasizes NO FIXES WITHOUT ROOT CAUSE FIRST.
Four-phase debugging framework that finds root causes before proposing fixes. Use when investigating bugs, errors, unexpected behavior, failed tests, or when previous fixes haven't worked.
Methodology for debugging non-trivial problems systematically. This skill should be used automatically when investigating bugs, test failures, or unexpected behavior that isn't immediately obvious. Emphasizes hypothesis formation, parallel investigation with subagents, and avoiding common anti-patterns like jumping to conclusions or weakening tests.
Systematic debugging process for Laravel applications - ensures root cause investigation before attempting fixes. Use for any Laravel issue (test failures, bugs, unexpected behavior, performance problems).
Question-only debugging mode that guides users to find root causes themselves through structured questioning. Never gives answers directly. Escalates to systematic-debugging after 12 questions if no progress. Use when: "rubber duck", "help me think through this bug", "debug with me", "walk me through debugging", "socratic debug", "think through this issue"
Interactive guide to repository workflow system: agents, skills, routing, and execution patterns. Use when user asks how the system works, what commands are available, or how to use brainstorm/plan/execute phases. Use for "how does this work", "what can you do", "explain workflow", "help me understand", or "show me the process". Do NOT use for actually executing workflows (use workflow-orchestrator) or debugging (use systematic-debugging).
Run Python quality checks with ruff, pytest, mypy, and bandit in deterministic order. Use WHEN user requests "quality gate", "lint", "verify code quality", "check python", or "pre-commit check". Use for pre-merge validation, CI/CD gating, or comprehensive code quality reports. Do NOT use for single-tool runs (run tool directly), debugging runtime bugs (use systematic-debugging), refactoring (use systematic-refactoring), or architecture review.
Post-mortem diagnostic analysis of failed or stuck workflows. Detects stuck loops, missing artifacts, abandoned work, scope drift, and crash/interruption patterns through git history and plan file analysis. Produces a structured diagnostic report with anomaly confidence levels, root cause hypotheses, and recommended remediation. READ-ONLY: never modifies files. Use for "forensics", "what went wrong", "why did this fail", "stuck loop", "diagnose workflow", "post-mortem", "workflow failure", or "session crashed". Do NOT use for debugging code bugs (use systematic-debugging), reviewing code quality (use systematic-code-review), or fixing issues (forensics only diagnoses).