MCPInstall

debug

Find and fix the root cause when something breaks: a failing test, a broken build, a bug report, or behavior that doesn't match expectations.

Installs
191
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/owainlewis/blueprint --skill debug
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads debug automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Debug

  1. Reproduce the failure. If you cannot, keep gathering information and report what you observed.
  2. Trace it to the root cause and explain why it happens.
  3. Add a small failing regression test when practical, then make the smallest fix that passes it. If no useful test is practical, say why and verify another way.
  4. Run relevant checks. Report the cause, the fix, how it was verified, and anything still unexplained.

Rules

  • Fix the cause, not the symptom. Do not delete the failing check, swallow the error, or weaken the assertion unless that is the real fix.
  • One bug at a time.
  • Do not pull unrelated failures or flaky infrastructure into the task.
  • Stop when the fix needs a product or code-owner decision.

FAQ

What does the debug skill do?

Find and fix the root cause when something breaks: a failing test, a broken build, a bug report, or behavior that doesn't match expectations.

How do I install debug?

Run npx skills add https://github.com/owainlewis/blueprint --skill debug in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/debug/ (personal) or .claude/skills/debug/ (project).

Which AI agents can use debug?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is debug safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains debug?

It is published by owainlewis in owainlewis/blueprint. It has 191 recorded installs.

More from owainlewis/blueprint

View all →

review

owainlewis/blueprint

Uses a fresh agent to review an implementation change without editing it. Checks behavior, security, regressions, complexity, tests, docs, and missing proof. Use for code, PR, diff, security, second-opinion, or pre-merge reviews.

plan

owainlewis/blueprint

Turns a reviewed spec or decided brief into ordered tasks for separate agent runs. Use for implementation tasks, tracker tickets, or useful milestones. Do not use for one coding task or its short execution outline.

task-to-pr

owainlewis/blueprint

Open the skill to read its SKILL.md instructions.

spec

owainlewis/blueprint

Open the skill to read its SKILL.md instructions.

tdd

owainlewis/blueprint

Open the skill to read its SKILL.md instructions.

Testing & QA371 installs

refactor

owainlewis/blueprint

Improve the shape of existing code without changing behavior.

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

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