Loading...
Loading...
Found 97 Skills
Systematically debug and diagnose issues methodically. Uses diagnostic techniques to identify root causes and implement fixes.
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
Fixes GitHub issues with parallel analysis. Use to debug errors, resolve regressions, fix bugs, or triage issues.
Diagnose and fix bugs with root-cause analysis and verification. Use when you have a concrete issue report, failing behavior, runtime error, or test regression that should be resolved safely. For ambiguous, high-risk, or broad-scope issues, stop and route to write-plan first.
Dispatch independent subagents in parallel for unrelated problems spanning different subsystems. Use when 2+ failures have independent root causes, multiple subsystems are broken independently, or user requests concurrent investigation. Use for "parallel", "multiple failures", "independent bugs", "fix these concurrently". Do NOT use for related failures, shared-state problems, or exploratory debugging where root cause is unknown.
Use when encountering any bug, test failure, or unexpected behavior. Enforces a strict reproduce-first, root-cause-first, failing-test-first debugging workflow before fixing.
Verify whether a GitHub issue is fixed in the local codebase. User provides a GitHub issue URL, the skill fetches it, extracts reproduction steps, builds the product from source, runs the reproduction steps, and reports whether the issue still exists or not.
Watch a bug video, screen recording, or screenshot, understand what's broken, find the relevant code, implement a fix, and raise a PR. Supports Loom, YouTube, and local files. Uses Gemini Flash for video understanding.
Reads documented bugs from bugs.md, analyzes root causes, implements fixes with regression tests, and validates the full test suite. Prioritizes fixes by severity (high to low). Updates bugs.md with correction status and generates a final bugfix report. Use when the user asks to fix bugs, resolve issues, or run the bugfix workflow for a feature. Do not use for new feature implementation, code review, or QA testing.
Use when implementing any feature or bugfix, before writing implementation code
Generates before/after verification pairs for loom plans. Proves a stage actually changed system behavior by capturing state before and after implementation. Use for delta-proof verification — proving new commands, endpoints, modules, or bug fixes work by comparing system state.
FORGE Quick Track — Spec + direct implementation for bug fixes and small changes. Usage: /forge-quick-spec "change description"