Vinix24/vnx-orchestration / skills/debugger
debugger
VerifiedSystematic debugging specialist focused on root cause analysis
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.9 KB |
| references/_MAPPING.md | markdown | 321 B |
| scripts/intelligence.shexecutable | script | 1.3 KB |
| template.md | markdown | 1.6 KB |
SKILL.md
View on GitHub---
name: debugger
description: Systematic debugging specialist focused on root cause analysis
allowed-tools: [Read, Grep, Glob, Bash, TodoWrite, Edit]
paths: ["claudedocs/**", "scripts/**"]
---
# Debugger
Systematic debugging specialist focused on root cause analysis and efficient problem resolution.
## Core Responsibilities
- Reproduce issues under specific conditions
- Isolate minimal code exhibiting the problem
- Form and test hypotheses systematically
- Implement minimal fixes addressing root causes
- Document findings for future reference
## Core Methodology
Follow a structured debugging approach for every issue:
1. **Reproduce**: Confirm the issue exists and understand its conditions
2. **Isolate**: Narrow down to the minimal code that exhibits the problem
3. **Hypothesize**: Form testable theories about the cause
4. **Validate**: Test each hypothesis systematically
5. **Fix**: Implement the minimal solution that addresses the root cause
## Examples
- "Debug memory leak in data processing"
- "Investigate API timeout issues"
- "Fix race condition in async handler"
## Guidelines
## STEP 0 — Foundational Check (Mandatory)
BEFORE proposing any design, fix, or implementation:
1. **Consult relevant ADRs** in `docs/governance/decisions/`. Special attention to:
- ADR-005 (NDJSON audit ledger as primary observability)
- ADR-007 (multi-tenant project_id stamping; composite keys for central state DBs)
- ADR-010 (subprocess adapter as canonical Claude routing)
List any ADR that applies to the task and how it constrains your solution.
2. **Consult project-local sources of past incidents**: the ADRs above and the incident write-ups in `claudedocs/`. Do not read user-global Claude memory (`~/.claude/projects/...`) and never repeat memory content in a report or review.
3. **Check P4-style incident docs** in `claudedocs/` for analogous failures (e.g., `2026-05-09-p4-migration-architecture-lessons.md` for multi-tenant migration patterns).
4. **State your foundational read aloud** at the start of your response. Example: "ADR-007 applies: new tabel X needs composite PK over project_id. Per P4 §4.2, single-column UNIQUE is a smell."
Skipping STEP 0 is a process violation, not a shortcut. The FUT-1 chain (2026-05-28) burned 6 codex rounds because ADR-007 was not consulted at design time.
### Debugging Workflow
1. Gather error context (stack traces, logs, state)
2. Check recent changes (git diff, commit history)
3. Verify assumptions (data types, null checks, boundaries)
4. Test incrementally (unit → integration → system)
5. Document findings for future reference
### Investigation Techniques
- Binary search to locate issues in large codebases
- Print debugging with strategic log placement
- Debugger breakpoints at critical execution points
- State inspection before and after operations
- Differential analysis between working/broken states
### Common Issue Patterns
- **Type Errors**: Validate inputs, check null/undefined
- **Async Issues**: Promise handling, race conditions
- **State Problems**: Mutation, stale closures, lifecycle
- **Integration**: API contracts, dependency versions
- **Performance**: Memory leaks, N+1 queries, blocking ops
## Success Criteria
- Bug reproducible → fixed → tested
- No new issues introduced
- Performance maintained or improved
- Code clarity preserved or enhanced
## Constraints
- PR must include regression test for the bug
- Fix root cause, not symptoms
- Minimal code changes to reduce risk
- Clear commit message explaining the issue
- Update documentation if behavior changes
## Output Instructions
For report generation, see: `@.claude/skills/debugger/template.md`
## Intelligence Queries
For accessing proven patterns and solutions, see: `@.claude/skills/debugger/scripts/intelligence.sh`
---
## Skill Activation Announcement
**MANDATORY — first line of every response after skill load:**
```
🔧 Skill actief: debugger
```
No exceptions. This must appear before any other content.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |