By avovello
Systematic bug fixing with reproduction, root cause analysis, and team-based fix+review loops
Reproduces bugs by finding relevant code, creating failing tests, or documenting exact reproduction steps. Use as the first step when investigating a bug report.
Traces execution paths and identifies root causes given reproduction evidence. Assesses impact and proposes a fix approach. Use after reproducer has confirmed the bug.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub avovello/cc-plugins --plugin bugfixQuality assurance orchestrator with dynamic skill discovery, prompt-based routing, and do-loop agent teams for test writing, execution, and browser testing
Code review with focused investigation and parallel specialized reviewers for security, architecture, performance, and bug detection
Claude Certified Architect – Foundations exam preparation with interactive training, mock exam simulation, and performance analysis
Systematic feature development with codebase exploration, architecture design, and team-based implementation loops (SOLID, Clean Architecture, Design Patterns, DDD)
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
Systematically debug issues with step-by-step troubleshooting approaches.
Core development agents and code quality hooks
Debugging workflows with competing hypothesis investigation via parallel subagents
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions. Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.