Agent Plugins Marketplace
← All plugins

debugging

v0.3.0

Six skills for finding the cause of a failure: minimise a bug reproduction, cluster log lines, find flaky tests in JUnit XML, explain a stack trace, summarise a py-spy, pprof or cProfile profile, and work a memory leak checklist.

Claude Code6 Skills

By Muhammad Basit AliLicense: MIT0 GitHub starsUpdated 2 weeks ago

Directory evidence

Runtimes
Claude Code
Parsed components
6 skill or MCP entries
Source updated
Oct 4, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install debugging for Claude Code

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install debugging-3@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/basitalisandhu/claude-dev-skills

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/debugging/.

Plugin files

plugins/debugging/
├── .claude-plugin/plugin.json
├── skills/bug-repro-minimiser/SKILL.md
├── skills/flaky-test-hunter/SKILL.md
├── skills/log-triage/SKILL.md
├── skills/memory-leak-checklist/SKILL.md
├── skills/perf-profile-reader/SKILL.md
└── skills/stack-trace-explainer/SKILL.md

Included Skills6

bug-repro-minimiserskills/bug-repro-minimiser/SKILL.md

Turn a vague bug report into the smallest reliable reproduction: a single command or test that fails every time, with the environment, input and expected versus actual result pinned down. Use when a bug report says "sometimes", "on my machine" or "it just crashes", before any fix is attempted, or when a fix needs a regression test. Not for performance regressions (use perf-profile-reader) and not a debugger tutorial.

flaky-test-hunterskills/flaky-test-hunter/SKILL.md

Find tests that pass and fail without code changes by comparing JUnit XML reports from several runs with a bundled script, then classify each flaky test by cause (ordering, timing, shared state, resources, environment) and prescribe the fix. Use when CI fails intermittently, when someone asks "is this test flaky?", or to quarantine and track flaky tests. Not for tests that fail every time (that is a bug, use bug-repro-minimiser).

log-triageskills/log-triage/SKILL.md

Reduce a large log file to its distinct message templates with counts, levels, first and last occurrence and attached stack traces using a bundled clustering script, then rank what to investigate. Use when handed a log dump, a failing CI log or "the logs are full of errors" and asked what is going on. Not for log shipping or alerting setup, or for binary or structured-only formats without a text line per event.

memory-leak-checklistskills/memory-leak-checklist/SKILL.md

Diagnose a process whose memory grows over time with a fixed checklist: confirm it is a leak and not a cache or fragmentation, measure with the runtime's heap tools (tracemalloc, objgraph, Node heap snapshots, Go pprof heap, JVM histograms), find the retaining path, and fix the usual suspects (unbounded caches, listeners, closures, global registries, connection pools, large buffers). Use when asked "why does memory keep growing?", or when memory climbs until a restart or an out-of-memory kill. Not for CPU performance (use perf-profile-reader).

perf-profile-readerskills/perf-profile-reader/SKILL.md

Summarise a captured CPU profile (py-spy collapsed stacks or dump, Go pprof text, Python cProfile output) into the few functions that hold the time, separate busy from waiting, and name the optimisation to try first, using a bundled script. Use when someone has a profile and asks "where does the time go?", or before optimising anything. Not for taking the profile (instructions are included) and not for memory profiles (use memory-leak-checklist).

stack-trace-explainerskills/stack-trace-explainer/SKILL.md

Read a stack trace or crash report from any mainstream runtime (Python, JavaScript and Node, Java and JVM, Go, Rust, .NET, Ruby, PHP), identify the frame where the fault lives versus where it surfaced, explain the error type, and propose the next diagnostic step. Use when someone pastes a trace and asks "what does this error mean?" or where to look. Not for performance traces or profiles (use perf-profile-reader) and not for logs without a trace (use log-triage).

Plugin manifests1

plugins/debugging/.claude-plugin/plugin.json
{
  "name": "debugging",
  "displayName": "Debugging",
  "version": "0.3.0",
  "description": "Six skills for finding the cause of a failure: minimise a bug reproduction, cluster log lines, find flaky tests in JUnit XML, explain a stack trace, summarise a py-spy, pprof or cProfile profile, and work a memory leak checklist.",
  "author": {
    "name": "Muhammad Basit Ali",
    "url": "https://github.com/basitalisandhu"
  },
  "homepage": "https://github.com/basitalisandhu/claude-dev-skills",
  "repository": "https://github.com/basitalisandhu/claude-dev-skills",
  "license": "MIT",
  "keywords": [
    "debugging",
    "logs",
    "flaky-tests",
    "stack-traces",
    "profiling",
    "memory-leaks"
  ]
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[debugging on Agent Plugins Marketplace](https://pluginsmp.com/plugins/debugging-3)