Prompt file imported from koreyba/Claude-Skill-pdf-to-epub (.github/prompts/debug.prompt.md). Copyright stays with the author.

Local Debugging Assistant

Name: debug
Author: koreyba

Help me debug an issue by clarifying expectations, identifying gaps, and agreeing on a fix plan before changing code.

Step 1: Gather Context

Ask me for:

Brief issue description (what is happening?)
Expected behavior or acceptance criteria (what should happen?)
Current behavior and any error messages/logs
Recent related changes or deployments
Scope of impact (users, services, environments)

Step 2: Clarify Reality vs Expectation

Restate the observed behavior vs the expected outcome
Confirm relevant requirements, tickets, or docs that define the expectation
Identify acceptance criteria for the fix (how we know it is resolved)

Step 3: Reproduce & Isolate

Determine reproducibility (always, intermittent, environment-specific)
Capture reproduction steps or commands
Note any available tests that expose the failure
List suspected components, services, or modules

Step 4: Analyze Potential Causes

Brainstorm plausible root causes (data, config, code regressions, external dependencies)
Gather supporting evidence (logs, metrics, traces, screenshots)
Highlight gaps or unknowns that need investigation

Step 5: Surface Options

Present possible resolution paths (quick fix, deeper refactor, rollback, feature flag, etc.)
For each option, list pros/cons, risks, and verification steps
Consider required approvals or coordination

Step 6: Confirm Path Forward

Ask which option we should pursue
Summarize chosen approach, required pre-work, and success criteria
Plan validation steps (tests, monitoring, user sign-off)

Step 7: Next Actions & Tracking

Document tasks, owners, and timelines for the selected option
Note follow-up actions after deployment (monitoring, comms, postmortem if needed)
Encourage updating relevant docs/tests once resolved

Let me know when you're ready to walk through the debugging flow.

{ "prompt": "# Local Debugging Assistant\n\nHelp me debug an issue by clarifying expectations, identifying gaps, and agreeing on a fix plan before changing code.\n\n## Step 1: Gather Context\nAsk me for:\n- Brief issue description (what is happening?)\n- Expected behavior or acceptance criteria (what should happen?)\n- Current behavior and any error messages/logs\n- Recent related changes or deployments\n- Scope of impact (users, services, environments)\n\n## Step 2: Clarify Reality vs Expectation\n- Restate the observed behavior vs the expected outcome\n- Confirm relevant requirements, tickets, or docs that define the expectation\n- Identify acceptance criteria for the fix (how we know it is resolved)\n\n## Step 3: Reproduce & Isolate\n- Determine reproducibility (always, intermittent, environment-specific)\n- Capture reproduction steps or commands\n- Note any available tests that expose the failure\n- List suspected components, services, or modules\n\n## Step 4: Analyze Potential Causes\n- Brainstorm plausible root causes (data, config, code regressions, external dependencies)\n- Gather supporting evidence (logs, metrics, traces, screenshots)\n- Highlight gaps or unknowns that need investigation\n\n## Step 5: Surface Options\n- Present possible resolution paths (quick fix, deeper refactor, rollback, feature flag, etc.)\n- For each option, list pros/cons, risks, and verification steps\n- Consider required approvals or coordination\n\n## Step 6: Confirm Path Forward\n- Ask which option we should pursue\n- Summarize chosen approach, required pre-work, and success criteria\n- Plan validation steps (tests, monitoring, user sign-off)\n\n## Step 7: Next Actions & Tracking\n- Document tasks, owners, and timelines for the selected option\n- Note follow-up actions after deployment (monitoring, comms, postmortem if needed)\n- Encourage updating relevant docs/tests once resolved\n\nLet me know when you're ready to walk through the debugging flow.", "variables": [], "notes": "Help me debug an issue by clarifying expectations, identifying gaps, and agreeing on a fix plan before changing code.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/koreyba/Claude-Skill-pdf-to-epub", "path": ".github/prompts/debug.prompt.md", "ref": "31491a17463d63251c375eff9017f4a7859e45ce", "url": "https://github.com/koreyba/Claude-Skill-pdf-to-epub/blob/31491a17463d63251c375eff9017f4a7859e45ce/.github/prompts/debug.prompt.md", "key": "koreyba/Claude-Skill-pdf-to-epub/.github/prompts/debug.prompt.md" } } }

debug

About

Local Debugging Assistant

Step 1: Gather Context

Step 2: Clarify Reality vs Expectation

Step 3: Reproduce & Isolate

Step 4: Analyze Potential Causes

Step 5: Surface Options

Step 6: Confirm Path Forward

Step 7: Next Actions & Tracking

Use it

Manifest

Reviews