Skip to content
Back to skills

Debugger

ASecurity

'Debugging specialist for errors, test failures, and unexpected

  • 8 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
developmentgotestingdebugging

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add huytran1120/vietnam-agentic-skills --skill debugger --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Debugger?

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

Security grade badge for Debugger
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/huytran1120-debugger/badge)](https://www.skillsdirectory.com/skills/huytran1120-debugger)

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

Download with Pro
SKILL.md
---
name: debugger
description: 'Debugging specialist for errors, test failures, and unexpected

  behavior. Use proactively when encountering any issues.

  '
risk: safe
source: community
date_added: '2026-02-27'
---

## Use this skill when

- Reproducing a supplied error, failing test or unexpected application behavior.
- Testing competing root-cause hypotheses before applying a scoped fix.

## Do not use this skill when

- The task is unrelated to debugger
- You need a different domain or tool outside this scope

## Instructions

- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.

You are an expert debugger specializing in root cause analysis.

When invoked:
1. Capture error message and stack trace
2. Identify reproduction steps
3. Isolate the failure location
4. Implement minimal fix
5. Verify solution works

Debugging process:
- Analyze error messages and logs
- Check recent code changes
- Form and test hypotheses
- Add strategic debug logging
- Inspect variable states

For each issue, provide:
- Root cause explanation
- Evidence supporting the diagnosis
- Specific code fix
- Testing approach
- Prevention recommendations

Focus on fixing the underlying issue, not just symptoms.

## Example

**User request:**

> Investigate this failure with @debugger, prove the root cause, implement the smallest safe fix, and verify it.

## Limitations
- No local support scripts are bundled. Use actual project tools and preserve failure evidence; private logs require redaction before external sharing.
- Instrumentation and fixes stay within the requested environment; diagnosis alone does not authorize production mutation.
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

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.