PromptCreek
Sign up
Back to Skills
Engineering

Debug

Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

$ npx promptcreek add debug

Auto-detects your installed agents and installs the skill to each one.

What This Skill Does

This skill guides users through a structured debugging process to systematically find and fix issues. It emphasizes reproduction, isolation, diagnosis, and fixing, providing a framework for efficient problem-solving. It's helpful for any developer facing a bug or unexpected behavior.

When to Use

  • Troubleshoot a bug reported by a user.
  • Diagnose the root cause of an error message.
  • Isolate a performance bottleneck.
  • Debug a failing test case.
  • Understand unexpected behavior in a system.
  • Systematically resolve complex issues.

Key Features

Provides a structured 4-step debugging process.
Emphasizes reproducing the issue.
Guides isolation of the problematic component.
Aids in diagnosing the root cause.
Suggests fixes with explanations.
Prompts consideration of side effects and edge cases.

Installation

Run in your project directory:
$ npx promptcreek add debug

Auto-detects your installed agents (Claude Code, Cursor, Codex, etc.) and installs the skill to each one.

View Full Skill Content

/debug

> If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Run a structured debugging session to find and fix issues systematically.

Usage

/debug $ARGUMENTS

How It Works

┌─────────────────────────────────────────────────────────────────┐

│                       DEBUG                                        │


├─────────────────────────────────────────────────────────────────┤


│  Step 1: REPRODUCE                                                │


│  ✓ Understand the expected vs. actual behavior                   │


│  ✓ Identify exact reproduction steps                             │


│  ✓ Determine scope (when did it start? who is affected?)        │


│                                                                    │


│  Step 2: ISOLATE                                                   │


│  ✓ Narrow down the component, service, or code path             │


│  ✓ Check recent changes (deploys, config changes, dependencies) │


│  ✓ Review logs and error messages                                │


│                                                                    │


│  Step 3: DIAGNOSE                                                  │


│  ✓ Form hypotheses and test them                                 │


│  ✓ Trace the code path                                           │


│  ✓ Identify root cause (not just symptoms)                      │


│                                                                    │


│  Step 4: FIX                                                       │


│  ✓ Propose a fix with explanation                                │


│  ✓ Consider side effects and edge cases                          │


│  ✓ Suggest tests to prevent regression                           │


└─────────────────────────────────────────────────────────────────┘

What I Need From You

Tell me about the problem. Any of these help:

  • Error message or stack trace
  • Steps to reproduce
  • What changed recently
  • Logs or screenshots
  • Expected vs. actual behavior

Output

## Debug Report: [Issue Summary]


Reproduction


  • Expected: [What should happen]
    • 

  • Actual: [What happens instead]
    • 

  • Steps: [How to reproduce]
    • 



Root Cause


[Explanation of why the bug occurs]



Fix


[Code changes or configuration fixes needed]



Prevention


  • [Test to add]
    • 

  • [Guard to put in place]

If Connectors Available

If ~~monitoring is connected:

  • Pull logs, error rates, and metrics around the time of the issue
  • Show recent deploys and config changes that may correlate

If ~~source control is connected:

  • Identify recent commits and PRs that touched affected code paths
  • Check if the issue correlates with a specific change

If ~~project tracker is connected:

  • Search for related bug reports or known issues
  • Create a ticket for the fix once identified

Tips

  • Share error messages exactly — Don't paraphrase. The exact text matters.
  • Mention what changed — Recent deploys, dependency updates, and config changes are top suspects.
  • Include context — "This works in staging but not prod" or "Only affects large payloads" narrows things fast.
0Installs
0Views

Supported Agents

Claude CodeCursorCodexGemini CLIAiderWindsurfOpenClaw

Attribution

anthropics
anthropics/knowledge-work-plugins
MITadmin

Details

License
MIT
Source
admin
Published
3/18/2026

Tags

engineering

Related Skills

Agent Protocol

Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.

90
Alireza Rezvani
#c-level#c-level advisor

CTO Advisor

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.

20
Alireza Rezvani
#c-level#c-level advisor

Agent Workflow Designer

Agent Workflow Designer

10
Alireza Rezvani
#engineering