By udecode
Enforce a four-phase debugging process—root cause investigation, pattern analysis, hypothesis testing, implementation—to systematically resolve bugs, test failures, performance issues, and unexpected behaviors before applying fixes. Trace errors backward through call stacks, add instrumentation like stack traces, and analyze test outputs to identify invalid data sources in multi-component systems.
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 udecode/dotai --plugin debugTest-driven development workflow for writing tests before implementation - red-green-refactor cycle with deterministic unit tests
Dig into library source code - clone and explore repos to answer API questions
MCP servers for Codex integration
macOS notifications for Claude Code events
Complete development toolkit - documentation, PRDs, design docs, debugging, PR workflows, and planning
Test-driven development workflow for writing tests before implementation - red-green-refactor cycle with deterministic unit tests
Debug issues systematically with root cause analysis and execution tracing
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.
Verification-first engineering toolkit for Claude Code. 15 skills across a 5-phase spine (Investigate → Design → Implement → Verify → Ship), 8 specialist agents, an interactive setup wizard. Every skill has rationalizations + evidence requirements. Built for senior ICs and tech leads.
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
Systematic debugging, root cause analysis, log analysis, profiling, binary search debugging, and postmortem analysis.