By dean0x
Run proactive bug analysis on the current branch using static and semantic analysis tools, then synthesize results into an actionable bug report with incremental analysis support across commits.
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.
Process and fix code review issues with risk assessment - decides FIX vs TECH_DEBT based on impact
Debugging workflows with competing hypothesis investigation via parallel subagents
Self-review workflow: Simplifier + Scrutinizer for code quality
Codebase exploration with structured analysis and optional knowledge base creation
Multi-type research with parallel researchers and trust-aware synthesis
npx claudepluginhub dean0x/devflow --plugin devflow-bug-analysisComprehensive code review with parallel specialized agents covering security, architecture, performance, and more
Reviews code for real bugs: off-by-ones, null derefs, race conditions, swallowed errors. Skips style nitpicks.
Automated code review, security scanning, and quality enforcement
AI code review catches structural issues — null derefs, leaks, races — about 65% of real defects. The other 35% are intent violations: bugs only catchable when you know what the code is supposed to do. Quality Playbook derives behavioral requirements from your codebase AND your docs (specs, issues, chat history), then drives a six-phase review against them. Finds the bugs that look right but aren't.
Point it at a codebase and it figures out what's worth doing — bugs, perf, tech debt, what to build next — then writes plans any agent can execute. It can hand the work to a cheaper model and review the result. It never edits your code.
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.