Skip to content
Back to skills

893 Debugprompt 9448ef35

ASecurity

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

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
testingdebugging

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 893-debugprompt_9448ef35 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 893 Debugprompt 9448ef35?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 893 Debugprompt 9448ef35
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-893-debugprompt-9448ef35/badge)](https://www.skillsdirectory.com/skills/tools-only-893-debugprompt-9448ef35)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
# Local Debugging Assistant

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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.