Claude Skill

debug-live

Live debugging workflow - reproduce first, DebugMCP breakpoints, conversational state questions, isolated repair branch, before/after tests, repair report. Use for /debug and hard production bugs.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download navinspire-ia-navin-navin_skills_debug-live-e9c73a3.zip · 1 KB

navinspire-ia/navin 31 4 forks AGPL-3.0 Updated 4d ago

Part of navinspire-ia/navin — 182 skills

Install

skills CLI npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/debug-live

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart

Git git clone https://github.com/Navinspire-ia/navin.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Debug Live

Pipeline

Erreur → reproduce → mcp_status → breakpoint → inspect stack/vars → hypotheses
  → fix on isolated branch → tests → before/after → repair report

Tools

exec - repro script and test suite
debug_repair(action=mcp_status) - probe DebugMCP at http://127.0.0.1:3001/mcp
debug_repair(action=start_branch|status|report) - isolation + HTML report
MCP preset debugmcp (Settings → MCP): real DAP tools when the extension is up
- add_breakpoint, start_debugging, list_variable_names → get_variables_values
- evaluate_expression, step_*, continue_execution, pause_execution
ChatDBG-style: treat user questions about live state as first-class (why is user None here?) - answer with REAL evidence from stack/vars/evaluate

Rules

Never edit before a failing repro exists.
Call mcp_status before guessing - use live breakpoints when reachable.
Symptom ≠ root cause - keep asking until the earliest wrong state is clear.
Fetch variables by name only (least privilege) - do not dump entire scopes.
Put fixes on debug_repair(start_branch) unless the user forbids git.
Same command must fail before and pass after.
End with debug_repair(report) including findings + latent_bugs when known; File Preview opens automatically on debug-report-*.html.

Files (navin)

SKILL.md 1.6 KB

---
name: debug-live
description: Live debugging workflow - reproduce first, DebugMCP breakpoints, conversational state questions, isolated repair branch, before/after tests, repair report. Use for /debug and hard production bugs.
metadata: {"navin":{"emoji":"🪲","category":"devops"}}
---

# Debug Live

## Pipeline

```
Erreur → reproduce → mcp_status → breakpoint → inspect stack/vars → hypotheses
  → fix on isolated branch → tests → before/after → repair report
```

## Tools

- `exec` - repro script and test suite
- `debug_repair(action=mcp_status)` - probe DebugMCP at `http://127.0.0.1:3001/mcp`
- `debug_repair(action=start_branch|status|report)` - isolation + HTML report
- MCP preset **debugmcp** (Settings → MCP): real DAP tools when the extension is up
  - `add_breakpoint`, `start_debugging`, `list_variable_names` → `get_variables_values`
  - `evaluate_expression`, `step_*`, `continue_execution`, `pause_execution`
- ChatDBG-style: treat user questions about live state as first-class
  (`why is user None here?`) - answer with REAL evidence from stack/vars/evaluate

## Rules

1. Never edit before a failing repro exists.
2. Call `mcp_status` before guessing - use live breakpoints when reachable.
3. Symptom ≠ root cause - keep asking until the earliest wrong state is clear.
4. Fetch variables by name only (least privilege) - do not dump entire scopes.
5. Put fixes on `debug_repair(start_branch)` unless the user forbids git.
6. Same command must fail before and pass after.
7. End with `debug_repair(report)` including `findings` + `latent_bugs` when
   known; File Preview opens automatically on `debug-report-*.html`.