Slash Command

/debug

Systematically debug an issue using structured diagnosis.

Install

npx claudepluginhub radenadri/skills-alena

Flags

No model invocation

Details

Argument[error-message-or-description]

Prompt Preview

# /debug — Systematic Debugging

Diagnose and fix an issue using structured problem-solving.

## Instructions

1. **Reproduce** — Understand the issue from `$ARGUMENTS`:
   - What is the expected behavior?
   - What is the actual behavior?
   - When did it start? (check recent commits with `git log --oneline -20`)

2. **Isolate** — Narrow down the root cause:
   - Search for related error messages in the codebase
   - Trace the execution path from entry point to failure
   - Check recent changes: `git log --diff-filter=M --name-only -10`
   - Look for obvious culprits: typos, missing import...

Command Content

Other plugins with /debug

/debug

Diagnoses Claude Office add-in deployment issues like stale configs, connection failures, missing add-ins, and auth errors via admin triage playbook.

claude-in-office

7.3k

/debug

autoresearch/

Runs autonomous bug-hunting loop with scientific method and autoresearch iterations to find all bugs. Supports --fix, --scope, --symptom, --severity, --iterations flags.

autoresearch

3.3k

/debug

Invokes oac:debugger skill to diagnose bugs, test failures, or unexpected behavior exactly as specified, before any fix proposals.

oac

3.0k

/debug

commands/

Systematically debugs code issues via reproduce-isolate-analyze-hypothesize-test-fix process, delivering step-by-step plans, root causes, fixes, prevention, and regression tests.

octo

2.8k

/debug

Orchestrates four specialist agents to systematically debug a code task description, producing problem analysis, refined hypotheses, diagnostic plan, and user confirmation request.

essentials

2.4k

/debug

Invokes debug-like-expert skill to systematically debug the specified issue via evidence gathering, hypothesis testing, and verification.

Skill(debug-like-expert)

taches-cc-resources

1.7k

Stats

Stars0

Forks0

Last CommitMar 30, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

# /debug — Systematic Debugging Diagnose and fix an issue using structured problem-solving. ## Instructions 1. **Reproduce** — Understand the issue from `$ARGUMENTS`: - What is the expected behavior? - What is the actual behavior? - When did it start? (check recent commits with `git log --oneline -20`) 2. **Isolate** — Narrow down the root cause: - Search for related error messages in the codebase - Trace the execution path from entry point to failure - Check recent changes: `git log --diff-filter=M --name-only -10` - Look for obvious culprits: typos, missing import...

/debug — Systematic Debugging

Diagnose and fix an issue using structured problem-solving.

Instructions

Reproduce — Understand the issue from $ARGUMENTS:

What is the expected behavior?
What is the actual behavior?
When did it start? (check recent commits with git log --oneline -20)

Isolate — Narrow down the root cause:

Search for related error messages in the codebase
Trace the execution path from entry point to failure
Check recent changes: git log --diff-filter=M --name-only -10
Look for obvious culprits: typos, missing imports, wrong variable names

Diagnose — Identify the root cause:

Don't fix symptoms — find the actual cause
Check if the issue exists in tests (and if tests are passing incorrectly)
Verify assumptions about data shapes, API responses, and state

Fix — Apply the minimal correct fix:

Change the fewest lines possible
Don't refactor while debugging
Add a comment explaining WHY this was the fix if non-obvious

Verify — Confirm the fix works:

Run the relevant tests
Manually verify the fix addresses the original issue
Check for regression: did the fix break anything else?

Prevent — Add safeguards:

Write a test that would have caught this bug
Add error handling if the root cause was an unhandled edge case

/debug — Systematic Debugging

Diagnose and fix an issue using structured problem-solving.

Instructions

Reproduce — Understand the issue from $ARGUMENTS:
- What is the expected behavior?
- What is the actual behavior?
- When did it start? (check recent commits with git log --oneline -20)
Isolate — Narrow down the root cause:
- Search for related error messages in the codebase
- Trace the execution path from entry point to failure
- Check recent changes: git log --diff-filter=M --name-only -10
- Look for obvious culprits: typos, missing imports, wrong variable names
Diagnose — Identify the root cause:
- Don't fix symptoms — find the actual cause
- Check if the issue exists in tests (and if tests are passing incorrectly)
- Verify assumptions about data shapes, API responses, and state
Fix — Apply the minimal correct fix:
- Change the fewest lines possible
- Don't refactor while debugging
- Add a comment explaining WHY this was the fix if non-obvious
Verify — Confirm the fix works:
- Run the relevant tests
- Manually verify the fix addresses the original issue
- Check for regression: did the fix break anything else?
Prevent — Add safeguards:
- Write a test that would have caught this bug
- Add error handling if the root cause was an unhandled edge case