1,488 tagged Debugging, measured the same way as everything else here.
Browse within: claude-code-plugin 211agents 116ai-coding 107cli 88cursor 86LLM 83agentic-ai 75agent 55github-copilot 50mcp-server 49skills 47ai-tools 44code-quality 44plugin 35
Agent Claude Code
Use this agent to detect and analyze code bloat, bundle size issues, and technical debt in your codebase. Trigger this agent when: (1) files exceed 500 LOC, (2) during weekly code health scans, (3) before major releases, (4) after adding new dependencies, or (5) when build times increase unexpectedly. Examples…
gensecaihq/MCP-Developer-SubAgent
Agent Claude Code
MCP troubleshooting and debugging specialist for protocol issues, transport problems, and diagnostic analysis.
Agent Claude Code
Senior implementation specialist handling escalated complexity from developer failures.
Agent Claude Code
Performance audit — N+1 queries, unbounded loops, missing indexes, payload sizes, caching, pagination.
adrielp/ai-engineering-harness
Agent Claude Code
Analyzes codebase implementation details and explains how code works. Use this agent when you need to understand specific components, trace data flow, identify architectural patterns, or explain technical implementations. Provide detailed context about what you want analyzed for best results.
TashanGKD/tashan-cursor-skills
Agent Claude Code
A coding agent that fixes reported bugs using test-driven development, or TDD: reproduce the problem, write a failing test, change the code, and confirm the tests pass. It first checks what the affected feature is meant to do.
Agent Claude CodeCursor
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when the user hits an error, failing test, or bug.
Agent Claude Code
Run MegaLinter locally with npx mega-linter-runner (full flavor run or standalone single-linter image), digest the reports, and return only a compact error list. Use to keep verbose linter output out of the main context. Runs and reports only — never fixes source files.
Agent Claude Code
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.
Agent Claude Code
Use when a specific skill has recurring low grades, warning or critical status, regressions, or unclear failures after basic doctor/status review. Investigates logs, evals, audit history, and transcripts, then returns a root-cause report with exact next actions.
Agent Claude Code
An autonomous agent that explores the codebase and uses the LLM Council to reach a consensus on complex issues.
Agent Claude CodeCursor
Code search agent for exploring any codebase. Use for finding implementations, locating symbols, understanding how code works, or tracing references. Prefer over Bash/Read for exploratory codebase search.
Agent Claude Code
Debugging specialist for errors and test failures. Use when encountering issues.
daeryundf2-prog/LAZYANTIGRAVITY
Agent Claude Code
A read-only codebase navigation agent that finds where code, files, symbols, and behavior live. It searches the workspace and reports the relevant absolute paths without editing anything.
Agent Claude Code
Use this agent when encountering errors, test failures, unexpected behavior, or when RTK doesn't work as expected. This agent should be used proactively whenever you encounter issues during development or testing.\n\nExamples:\n\n \nContext: User encounters filter parsing error.\nuser: "The git log filter is crashing…
JHamidun/claude-code-config-pack
Agent Claude Code
Investigates bugs using scientific method, manages debug sessions, handles checkpoints. Spawned by /gsd:debug orchestrator.
Agent Claude Code
Master-level root cause analyst — Kodelyth. A decade-seasoned engineer who has debugged production incidents at $300B-scale companies under real pressure. Traces every bug to its exact origin through evidence and logic — never guesses, never patches symptoms, never stops until the root cause is understood. Use when a…
Agent Claude Code
You are an incident investigator agent. You can perform end-to-end incident investigation workflow that fetches logs and performs root cause analysis. Use when a user wants to investigate incidents, analyze job failures, fetch and analyze logs in one workflow, or debug infrastructure issues. Combines log-fetcher…
Agent Claude Code
Reviews always-on background software — launch agents, daemons, login items, menu bar apps, VPNs, sync clients — and says which ones are worth removing or disabling for battery. Needs judgment about what an app is for — runs on a mid-size model.
Agent Claude Code
Expert AMPL debugger for infeasibility, unboundedness, IIS, conflict analysis, and solve failures. Use when solveresult is infeasible, unbounded, limit, or failure; when the user mentions IIS, conflicting constraints, presolve, or "model won't solve". Readonly diagnosis — fixes are suggestions until verified.
Agent Claude Code
Proactively use when Codex wants a second implementation or diagnosis pass, needs deeper root-cause investigation, or should hand a substantial coding task to Claude Code through the ccrescue tool.
Agent Claude Code
Verifies blastproof changes — runs build/typecheck/vitest and E2E against examples/demo-app, files and retests defects in DEFECTS.md. Use after dev implements tasks. Only qa may close a defect; never edits product code.
microsoft/aibast-agents-library
Agent Claude Code needs its repo ✓ vendor
Autonomous steward for the CommunityRAPP installation. Use proactively for application health checks, code maintenance, diagnostics, security audits, deployment verification, and evolution planning. Invoke when the user mentions health issues, deployment problems, maintenance tasks, code quality, security concerns, or…
Agent Claude Code
A specialised helper for reviewing code changes, finding bugs, diagnosing causes, and challenging reported problems with counterexamples.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: