Skip to content

feat: debug-agent Claude Code plugin (debugger + Python/Go/Node skills + agents)#7

Merged
niradler merged 17 commits into
mainfrom
feat/claude-plugin
May 29, 2026
Merged

feat: debug-agent Claude Code plugin (debugger + Python/Go/Node skills + agents)#7
niradler merged 17 commits into
mainfrom
feat/claude-plugin

Conversation

@niradler
Copy link
Copy Markdown
Owner

Packages the dbga evidence-first debugger plus consolidated language skills and specialist agents as a distributable Claude Code plugin, giving a full design → develop → debug → verify → clean-up workflow for Python, Go, and Node/TypeScript.

Implements the spec/plan in docs/superpowers/ (borrow-and-refine from MIT sources wshobson/agents + VoltAgent).

What's in it

  • Plugin scaffold: repo-root .claude-plugin/marketplace.json (name dbga, source ./plugin) + plugin/.claude-plugin/plugin.json (name debug-agent, v0.1.0, MIT). README documents both install paths + the dbga/debug-agent/debug_agent name glossary.
  • Skills (plugin/skills/): debug-agent (moved from repo root — 5 refs updated), plus new slim-index python, go, node skills (all SKILL.md < 500 words) routing to language-specific references. Language-invariant discipline authored once in _shared/ (clean-code, evidence-first, dependency-hygiene) and cross-referenced by name.
  • Agents (plugin/agents/): architect (opus orchestrator, authored fresh) + python-expert / go-expert / node-expert (sonnet), each embedding the Evidence-First block.
  • Command: /debug-agent:setup (uv → pipx → pip installer, toolchain readiness report).
  • Docs: references/agent-teams.md (experimental parallel-debugging mode), THIRD_PARTY_NOTICES.md (verbatim MIT texts + per-file SHAs), CLAUDE.md "Python-only" line corrected to the multi-language reality.

Verification

  • claude plugin validate ./plugin passes; all 4 skills + 4 agents discovered and valid.
  • npx skills add <repo> --skill python|go|node|debug-agent each install standalone (resolved via marketplace.json — no --full-depth needed; Phase 0 verified empirically against skills CLI v1.5.0).
  • skill-creator quick_validate passes for all 4 skills.
  • Two-stage subagent review per phase (spec + quality); Phase B review caught and fixed 2 wrong Go dbga session shapes + dep-hygiene framing + Python/TS type examples.
  • Trigger-separation eval: 12/12 cross-skill negatives stay quiet (no mis-fire). Positive-trigger rate is unmeasurable on native Windows (harness select()-on-pipe bug → WinError 10038); needs WSL — documented in docs/superpowers/evals/RESULTS.md.
  • Behavioral test (buggy Python script, baseline vs with-skill): with-skill ran the real flow first and verified at the original fault (positive evidence-first delta); neither added stray comments.

Follow-ups (not in this PR)

  • Live claude --plugin-dir ./plugin /help + /agents listing and the architect-as-main-thread e2e are interactive checks to run post-merge.
  • Optional: regenerate positive trigger-rate numbers under WSL/Linux.
  • Tagging deferred until after merge.

niradler added 17 commits May 29, 2026 16:29
…ompts

Dogfooding the plugin's own agents on this repo surfaced a systemic gap: all four experts default to confident source-reading on review/audit tasks (no live failure to reproduce) without labeling confidence. node-expert shipped a HIGH-severity false positive that a single parser run disproved, and its proposed fix was behaviorally identical to the existing code.

Add a 'live-failure vs static review' mode to the shared evidence-first discipline and an in-body review/audit clause to python/go/node-expert and architect: label findings RUNTIME-VERIFIED vs INSPECTION-ONLY, prove or offer a repro for anything reproducible, and separate 'breaks today' from 'latent under a future/edge runtime'. Kept in agent bodies because dispatched agents were observed skipping reference loads.
Child-delegating adapters (vscode-js-debug) run the program in a child
session, so exception filters set on the parent at launch never bind.
Breakpoints were already stashed and replayed on the child; do the same
for exception filters. Without this, `--break-on-exception` was silently
dropped for Node. Stash `_exception_filters` at launch and replay them in
`_on_start_debugging` alongside breakpoints.
…E usage guidance

node-expert: make the top-level evidence stance unconditional (mirrors
python-expert rule #3) so the RUNTIME-VERIFIED/INSPECTION-ONLY labeling
discipline applies to review/audit tasks, not just crash-fix flows.

README: add usage guidance (architect delegation cliff, review-vs-debug
expectations, opus override for hard single-language tasks).
@niradler niradler merged commit 117ef8b into main May 29, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant