Bug-ticket workflow for development repos — capture bugs into planning/bugs/, dispatch to specialist remediation agents, document fixes, and ship releases.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin dev-debuggerCapture one or more bugs from the current project into standardized reports under planning/bugs/to-resolve/ in the target repository, then optionally hand off to the bug-manager agent.
Quick-path fix for a trivial bug. Skips the full capture → manager → reproducer → diagnoser pipeline and dispatches the patcher agent directly. Use for one-line typos, obvious null-checks, renamed identifiers, or other well-scoped trivial fixes.
Orchestrator agent for bug remediation. Reads a standardized bug report, triages complexity, and dispatches specialist sub-agents (reproducer, diagnoser, patcher, fix-documenter). Use when a captured bug (from /capture-bug) needs to be fixed and the workflow may benefit from staged investigation.
Specialist sub-agent that locates the root cause of a bug in the codebase. Does not patch. Invoked by the bug-manager orchestrator after reproduction.
Specialist sub-agent that writes a private post-mortem note after a bug fix is committed. Notes go to planning/bugs/resolved/ and are gitignored by default — intended as internal knowledge, not public-facing release notes. Invoked by the bug-manager after a successful patch.
Specialist sub-agent that makes the minimal code change to fix a bug, given a diagnosis. Invoked by the bug-manager orchestrator, or directly by the /patch command for trivial fixes.
Specialist sub-agent that reproduces a bug from its repro steps and reports what was observed. Does not diagnose or patch. Invoked by the bug-manager orchestrator.
Bug-ticket workflow for development repos. Capture bugs into the repo itself, dispatch specialist remediation agents, document fixes privately, and ship releases — all through Claude Code.
For system/runtime debugging (boot logs, crash diagnosis, slowdowns, deployment inspection) see the companion plugin
os-debugging-plugin. This plugin is scoped to code/app bug workflows in development repos.
/capture-bug — capture one or more bugs from the current repo into standardized reports under planning/bugs/to-resolve/ inside the repo. Sequential per-repo IDs, optional screenshots, optional hand-off to bug-manager./patch — quick path for trivial fixes (typos, off-by-ones, obvious null-checks). Skips the full pipeline and dispatches patcher directly.Orchestrator + specialist sub-agents:
bug-manager — the orchestrator. Reads a bug report, triages complexity, and dispatches sub-agents in sequence. Handles verification, commits, and the post-fix release protocol.reproducer — attempts to reproduce the bug from its steps and reports observed failure mode. Read-only on source.diagnoser — locates root cause with file_path:line_number evidence. Read-only on source.patcher — makes the minimal code fix and verifies. Can also be invoked directly via /patch.fix-documenter — after a successful fix, writes a private (gitignored) post-mortem note to planning/bugs/resolved/BUG-XXXX-notes.md covering root cause, false leads, watch-list, and lessons.Triage rules the bug-manager applies:
patcher → fix-documenterreproducer → diagnoser → patcher → fix-documenterBug reports are stored inside the target repository — not in a central location. This keeps bugs versioned alongside the code they concern.
<repo>/planning/bugs/
├── to-resolve/
│ ├── BUG-0001.md
│ ├── BUG-0002.md
│ └── screenshots/
└── resolved/
├── BUG-0000.md
└── BUG-0000-notes.md (private, gitignored by default)
On the first /capture-bug invocation in a repo, the command asks whether to commit planning/bugs/ (tracked in git, useful for team visibility) or gitignore it (local only, for public repos that shouldn't expose internal bug tracking). The private *-notes.md files written by fix-documenter are always gitignored regardless.
Each report uses YAML frontmatter (id, repo, status, severity, screenshots) and a standardized body (summary, repro steps, expected/actual, environment, remediation checklist).
After bug-manager verifies a fix, it follows the repo's release conventions:
/release, build-and-push-debian, create-package-release) when present.claude plugins install danielrosehill/dev-debugger-plugin
Restart Claude Code after installation.
MIT
Meta-prompting and spec-driven development system for Claude Code. Productivity framework for structured AI-assisted development.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Comprehensive PR review agents specializing in comments, tests, error handling, type design, code quality, and code simplification
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Comprehensive C4 architecture documentation workflow with bottom-up code analysis, component synthesis, container mapping, and context diagram generation
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claim