Tag: debugging

A complete development methodology for coding agents: brainstorm to clarify requirements, write an implementation plan, then build with subagents, with red-green TDD, systematic debugging and code review throughout. In the official Claude Code and Codex marketplaces.

A full development methodology for coding agents: brainstorm a design, break it into an implementation plan, dispatch subagents to build and review each task, with mandatory TDD and systematic debugging. Installed as a plugin, it injects its bootstrap automatically.

Matt Pocock's engineering skills: grill-me interrogates you to align on requirements, to-spec turns discussion into a spec, to-tickets breaks it into tickets, plus tdd, diagnosing-bugs, code-review and more. Run setup-matt-pocock-skills once per repo first.

A four-phase root-cause debugging method: investigate the root cause, compare against working examples, test one hypothesis at a time, then fix the root cause. Guessing at code changes before locating the cause is not allowed. From the Superpowers workflow.

A disciplined process for hard bugs and performance regressions: build a reliable reproduction loop, reproduce and minimize, form hypotheses, instrument to verify, then fix and add a regression test, redacting secrets in output. By Matt Pocock.

After code changes, has the agent check routes, errors and page behavior in the running Next.js app via /_next/mcp and agent-browser to confirm the change really works. Maintained by Next.js; needs Next.js 16.3+ (Turbopack) and agent-browser.

Teaches agents to use the Chrome DevTools MCP efficiently: snapshot first to get element uids, screenshot only when needed, paginate and filter large output, inspect CSS and test browser extensions. Needs chrome-devtools-mcp configured; maintained by the Chrome DevTools team.

Official Chrome plugin bundling the Chrome DevTools MCP with debugging skills for accessibility, LCP and memory leaks: lets agents drive and inspect a real Chrome and analyze network requests, console logs and performance traces. Collects usage stats by default; can be disabled.

Lets agents control and inspect a real Chrome: read the console and network requests, take screenshots, and record performance traces with optimization suggestions. Maintained by the Chrome DevTools team.

Orchestrates multi-agent teams using Claude Code's experimental Agent Teams feature: parallel multi-angle code review, competing-hypothesis debugging and feature work split by file ownership. Enable CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS first.

Alibaba's open-source Java production diagnostics tool: inspect method arguments and timing, threads and GC, class loading and decompiled code, and generate flame graphs without changing code or restarting the JVM. Supports JDK 8+ via an interactive CLI.

Everyday software engineering plugin: standup summaries, code review, structured debugging, architecture decision records, incident response and pre-deploy checks. Official from Anthropic, built mainly for Cowork but also usable in Claude Code.

Open-source reverse engineering framework and CLI: disassemble, debug, emulate and patch binaries across many architectures and file formats, scriptable through r2pipe or built-in JavaScript.

Adds a structured dev process to Claude Code: 30 /sc slash commands for brainstorming, implementation, testing, troubleshooting and research, 20 domain expert subagents and 7 behavior modes, with optional MCPs like Context7. Installs via pipx; a marketplace version is in progress.

Pressures the agent with big-tech PUA and PIP-style rhetoric plus structured debugging steps and initiative checks, pushing it to change approach after failures and show evidence before claiming done. Modes include always-on, encouragement and P9 lead. Works with Claude Code, Codex and more.

Bundles 60+ full-stack specialist skills into one plugin: experts for 12 languages including Python, TypeScript, Go, Rust and Java, and frameworks like React, Django and Spring Boot, activated automatically by request. Also includes Jira and Confluence workflow commands (needs Atlassian MCP).

Connects to the Arize Phoenix observability platform so agents can query LLM traces and sessions, manage prompts, browse datasets and read experiment evaluation results. Maintained by Arize; needs a self-hosted or cloud Phoenix instance.

Lets Claude Code, Codex and other agents call Gemini, GPT, Ollama and other models to collaborate on code review, debugging, planning and multi-model consensus, and can bridge to other CLI agents. Configure at least one provider (API key or local Ollama). Formerly Zen MCP.

The official MCP debugging tool: connect to any MCP server through a web UI, CLI or terminal UI to list and call its tools, resources and prompts. CLI mode outputs JSON, suited to scripts and CI smoke tests.

Tencent's open-source browser bridge: through the bsk CLI and a Chrome/Edge extension, agents use your logged-in accounts in a separate visible window to browse, fill forms and take full-page screenshots, and correlate network requests with console output to debug sites.

Open-source visual traceroute that shows IP geolocation, AS number and carrier for every hop, with continuous MTR probing and JSON output; the full edition can also be deployed as an MCP server.

Tests and debugs a locally running frontend with Codex's Browser plugin or Playwright: checks blank pages, framework and console errors, captures screenshots, re-verifies after fixes and writes a QA report. Maintained by OpenAI; formerly playwright-interactive in openai/skills.

OpenAI's official Codex plugin for macOS apps: building and running, SwiftUI scenes and AppKit interop, testing and troubleshooting, signing, notarization and packaging, and logging instrumentation. Requires macOS and Xcode; Codex only.

OpenAI's official Codex plugin for iOS: SwiftUI UI work and refactoring, App Intents, simulator debugging, performance profiling and memory leak hunting, with XcodeBuildMCP built in. Requires macOS and Xcode; Codex only.