1,660 free skills
Debugging skills
Skills for systematic debugging — reproducing bugs, reading stack traces, bisecting regressions, and diagnosing flaky failures.
Sourced from real, public repositories — synced daily, never invented.
1,660 free skills
Skills for systematic debugging — reproducing bugs, reading stack traces, bisecting regressions, and diagnosing flaky failures.
Sourced from real, public repositories — synced daily, never invented.
15 tools across six categories
13 of them never send your data anywhere
Free · No signup · No trial clock
SEE THE DIRECTORY
debugging-mastery
danik911/thesis_project
Systematic debugging methodologies for finding and resolving complex bugs. Use PROACTIVELY when encountering difficult bugs, mysterious failures, or issues that resist simple fixes. MUST BE USED when debugging spans multiple files, involves race conditions, or has eluded initial investigation attempts.
debugging-and-error-recovery
shennawardana23/skillme
Enforces a stop-the-line triage protocol across failure classes — test failures, build breaks, runtime errors, and production incidents — using bisection, safe-fallback design, and instrumentation lifecycle management. Use when any unexpected failure appears and the question is "what class of failure is this and what's the triage tree", not root-causing one already-identified bug (use debug for that tight four-phase loop instead).
flaky-debug
clipboardhealth/skills
Debug and fix flaky Playwright, NestJS, React, and unit tests.
flaky-tests
gabrielbauman/skills
Treat an intermittently failing test as a bug to fix, not a nuisance to rerun: quarantine it visibly with an owner and expiry, reproduce with a counted loop, diagnose against the usual suspects (sleep-based waits, test order and shared state, unseeded randomness, real clocks and networks, leaked resources), and fix the mechanism instead of widening the timeout. Use whenever a test fails intermittently or only in CI, passes on retry, fails only in parallel runs or after other tests, or when asked to fix, skip, or delete a flaky test, add automatic retries, or investigate CI instability.
flaky-test-triage
lewisth/ado-skills
Triage unstable test failures by gathering evidence, classifying flaky versus real versus environmental issues, inspecting code history, and proposing the right response. Use when the user asks about flaky tests, CI flakes, quarantining tests, recurring test failures, unstable pipelines, or failure triage workflows.
flaky-tests
kvet/queuert
Identify flaky tests by running tests multiple times and analyzing intermittent failures. Use when investigating test reliability.
flaky-test-detector
maxrall-inc/nexrall-skills
Diagnose tests that pass and fail non-deterministically, instead of blaming the code under test or "fixing" the test. Use when a test fails sometimes but not others, when the user says a test is "flaky", "unstable", "passes locally but fails in CI", or when the same test gives different results on repeated runs.
test-flakiness
freedomportal/ccgs-technica-edition
Detect non-deterministic (flaky) tests by reading CI run logs or test result history. Aggregates pass rates per test, identifies intermittent failures, recommends quarantine or fix, and maintains a flaky test registry. Best run during Polish phase or after multiple CI runs.
flaky-test-diagnosis
sjinks/ai-skills
Use when: a test passes and fails non-deterministically (flaky), fails only under load/parallelism/sanitizers, fails in CI but not locally, or fails depending on run order - diagnosing timing races, order dependence, shared global state, unseeded RNG, real-clock/timezone/locale reliance, real network/filesystem dependence, and hash/iteration-order assumptions, then making it deterministic.
flaky-test-healer
shreyasbh02/ai-skills-collection
Analyzes and refactors flaky UI tests written in Selenium WebDriver with Java.
Debugging
hiehoo/forex-rebate-bot
Debug systematically with root cause analysis before fixes. Use for bugs, test failures, unexpected behavior, performance issues, call stack tracing, multi-layer validation.
debug-test
tzolkinb/skills
Automatically diagnose a failing Playwright test — reads files directly, applies QA heuristics, routes to the Playwright healer or diagnosing-bugs, and classifies what the healer changed before calling it fixed, flagging 🔁 when the same test keeps getting healed for the same reason (read from git history, nothing stored). Also has a flake mode (detects, quarantines, routes flaky tests — Playwright or Cypress) and a drift mode (classifies an already-red test as external drift vs local regression and surfaces the mismatch for a human to dispose).
playwright-expert
zacklecon/claude-skills
Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke for browser automation, E2E tests, Page Object Model, test flakiness, visual testing.
memory-leak-debugging
dzianisv/chrome-devtools-mcp
Diagnoses and resolves memory leaks in JavaScript/Node.js applications. Use when a user reports high memory usage, OOM errors, or wants to analyze heapsnapshots or run memory leak detection tools like memlab.
memory-leak-debugging
morningstar0709/trae-skills
Diagnose JavaScript, browser, and Node.js memory leaks in Trae with Chrome DevTools MCP and memlab-oriented workflows. Use when the user reports high memory usage, OOM errors, heap snapshots, detached DOM nodes, growing memory, or Chinese requests such as 内存泄漏, 内存占用高, 页面越用越卡, 分析 heapsnapshot, or 排查 Node 内存问题.
memory-leak-hunter
mithrandir21/game-deals-android-app
Triage Android memory leaks from LeakCanary reports and heap dumps — lifecycle-bound listeners, static holders, retained Compose state, Bitmap leaks, coroutine scope leaks, and KMP shared-state holds. Use whenever the user mentions LeakCanary output, "leaked Activity", "leaked Fragment", "OOM", "heap dump", `.hprof`, or memory growth over time. Also use when reviewing code that registers listeners, observers, or callbacks across lifecycle boundaries.
debugging
pluginagentmarketplace/custom-plugin-cpp
>
memory-profiler
wellux/claude-code-deprecated
>
leak-audit
nbialk/eval-skills
>-
flutter-memory-leak
yendangn/flutter-app-builder
Use this skill when detecting or fixing Flutter memory leaks — disposing controllers, cancelling StreamSubscriptions, leak_tracker integration, Flutter DevTools memory profiling, StatefulWidget dispose, AnimationController leaks, TextEditingController leaks, ScrollController leaks, FocusNode leaks, StreamController leaks, BuildContext leaks, widget test leak assertions, or auditing a Flutter app for memory leak sources.
ios-debugging
abanoub-ashraf/manus-skills-import
Master iOS debugging with LLDB, Instruments, crash log analysis, and debugging techniques. Use when debugging crashes, memory issues, performance problems, or understanding code execution. Triggers on debug, LLDB, breakpoint, crash, Instruments, debugger, console, stack trace, symbolicate, memory graph.
detect-ssr-leak
vonajs/vona
Detect server-side memory leaks in Node.js SSR services. Use when user asks to "check for memory leak", "detect leak", "SSR memory leak", "内存泄漏", or wants to diagnose growing memory usage on a Node.js server. TRIGGER when user mentions memory leak detection, especially for SSR/Vue/React server-side rendering.
debugging-troubleshooting
abhirkeesara/test-automation-skills
>
debugging-moonbeam
manuelmauro/moonbeam-skills
Debugs issues in the Moonbeam parachain including runtime panics, EVM execution failures, XCM message delivery problems, and client-side errors. Use when encountering transaction failures, unexpected behavior, state inconsistencies, block production issues, or RPC errors.
debugging-strategies
coppermare/skillverse
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
debugging-toolkit-smart-debug
ngxtm/devkit
Use when working with debugging toolkit smart debug
debugging-strategies
mwathiben/hush-private-bookmarks
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
debugging
andreaswasita/copilot-agents-dojo
Systematic root-cause investigation for hard bugs.
debugging-toolkit-smart-debug
kunanonj/claude-skills-hub
Use when working with debugging toolkit smart debug
Debugging
hotriluan/alkana-dashboard
Debug systematically with root cause analysis before fixes. Use for bugs, test failures, unexpected behavior, performance issues, call stack tracing, multi-layer validation.
debugging
jyadegari/agent-skills
Systematically diagnose and fix broken code. Use when something is failing, behaving unexpectedly, or throwing an error.
prod-debug
quilibrium-community/quily
Debug live production issues on quily.quilibrium.one (Vercel-hosted Next.js chatbot) — fetch runtime logs via Vercel CLI, hit the live API autonomously with the debug bypass, and read the structured diagnostics embedded in the chat stream. Use when the user reports the bot is broken, giving empty answers, returning garbage, or behaving unexpectedly in production. Trigger on phrases like "the bot is broken", "empty answers on the web app", "check what's going on in prod", "debug production", "why is the chatbot failing", "prod-debug".
generators-debug-menu
autisticaf/claude-code-apple-dev-plugin
Generates a developer debug menu with feature flag toggles, environment switching, network log viewer, cache clearing, crash trigger, and diagnostic info export. Only included in DEBUG builds. Use when user wants a debug panel, dev tools menu, or shake-to-debug functionality.
debugging-apex-logs
rodrigotxra/salesforce-skills
Salesforce debug log analysis and troubleshooting with 100-point scoring. TRIGGER when: user analyzes debug logs, hits governor limits, reads stack traces, or touches .log files from Salesforce orgs. DO NOT TRIGGER when: running Apex tests (use running-apex-tests), generating or fixing Apex code (use generating-apex), or Agentforce session tracing (use observing-agentforce).
debugging-apex-logs
sshvarzman-salesforce/claude-skills
Salesforce debug log analysis and troubleshooting with 100-point scoring. TRIGGER when: user analyzes debug logs, hits governor limits, reads stack traces, or touches .log files from Salesforce orgs. DO NOT TRIGGER when: running Apex tests (use running-apex-tests), generating or fixing Apex code (use generating-apex), or Agentforce session tracing (use observing-agentforce).
log-analysis
agenticdevops/devops-execution-engine
Cross-platform log analysis patterns and techniques
log-analysis
fuzzdkk/dfir-skills
Analyze system and security logs (auth.log, syslog, Windows EVTX, Apache/Nginx, JSON logs). Detect brute force, lateral movement, privilege escalation, and anomalous activity.
log-analysis
do360now/security-agents
>
sf-debug
yanushl/brownfieldproject
>
sf-debug
manoelcalixto/sf-skills
>
platform-apex-logs-debug
cs-tool/claude-skills
Salesforce debug log analysis and troubleshooting with 100-point scoring. TRIGGER when: user analyzes debug logs, hits governor limits, reads stack traces, or touches .log files from Salesforce orgs. DO NOT TRIGGER when: running Apex tests (use platform-apex-test-run), generating or fixing Apex code (use platform-apex-generate), or Agentforce session tracing (use agentforce-observe).
platform-apex-logs-debug
dhoffritz/sf-skills
Salesforce debug log analysis and troubleshooting with 100-point scoring. TRIGGER when: user analyzes debug logs, hits governor limits, reads stack traces, or touches .log files from Salesforce orgs. DO NOT TRIGGER when: running Apex tests (use platform-apex-test-run), generating or fixing Apex code (use platform-apex-generate), or Agentforce session tracing (use agentforce-observe).
regression-compare
aethis-ai/aethis-skills
Compare decision behavior between rule versions using a stable corpus and highlight regressions.
debugging-wizard
agentic-assets/agent-skills
Use when investigating errors, analyzing stack traces, or finding root causes of unexpected behavior. Invoke for error investigation, troubleshooting, log analysis, root cause analysis.
trace
arielbk/trace-v2
Bind the current session to a Trace task, and re-enter prior task context. Use when the user names a specific piece of work they are starting, resuming, or continuing — including "scope out X", "define a new X", "plan the work for X", "build X", "I need to build X from scratch", "tackle X", "add X to Y", "work on X", or "get back to X". Covers features, bugs, and refactors. Trace fires FIRST whenever the user commits to a new, named piece of work — whether or not they say "feature" or "task", and even when they also want to brainstorm, scope, or plan it — so the session is bound before any planning or creative skill runs. Does NOT apply when actively debugging or investigating a running system ("this endpoint is throwing errors", "help me debug X"), nor when the user is explicitly deferring the build to explore options first ("before we build anything, let's explore the design space") — neither is a committed new piece of work. Also use when explicitly asked to bind a session to a task, or when session-start context reports no active task during real project work.
bisect
sirius-db/sirius
>
regression-hunt
webdevcody/go-mailing-list
Find the commit that introduced a regression — a bug in a feature that used to work and is now broken. Walks git history with log/blame and escalates to manual git bisect when commit messages don't reveal the cause. Stops at root-cause identification; user decides the fix. Use when the user says "this used to work", "worked yesterday/last week", "broken since [update/deploy]", "regression", "what changed", or reports a feature that previously functioned and now doesn't. Do NOT use for new features that never worked — that's debugging, not regression hunting.
regression-suite
leijieming/claude-code-game-studios
Map test coverage to GDD critical paths, identify fixed bugs without regression tests, flag coverage drift from new features, and maintain tests/regression-suite.md. Run after implementing a bug fix or before a release gate.
regression-test
utmostcreator/awesome-ai-utmostcreator
Use when the main task is to create a failing or proving regression test for a reported bug or edge case
test-flakiness
leijieming/claude-code-game-studios
Detect non-deterministic (flaky) tests by reading CI run logs or test result history. Aggregates pass rates per test, identifies intermittent failures, recommends quarantine or fix, and maintains a flaky test registry. Best run during Polish phase or after multiple CI runs.
flaky-test-hunter
kao273183/qa-claude-skill
從 CI 跑歷史紀錄統計每個測試的失敗率，識別 flaky test（重跑就過的不穩定測試）、給出修復建議、自動標記到 quarantine（隔離區）讓 CI 不被假失敗阻擋。支援 GitHub Actions / GitLab CI / CircleCI / Jenkins JUnit XML / pytest-xdist 失敗紀錄。當使用者提到「flaky test / 不穩定測試 / 假失敗 / retry 才過 / CI 不穩 / quarantine test / 隔離測試 / 找出 flaky / 修 flaky」時觸發。配套：smoke-test-analyzer（flaky 不該進 T0）、test-review（審 flaky pattern）、bug-report（追 flaky bug）。
Debugging
donganhvuphp/claude-skills-lord
Systematic debugging framework ensuring root cause investigation before fixes. Includes four-phase debugging process, backward call stack tracing, multi-layer validation, and verification protocols. Use when encountering bugs, test failures, unexpected behavior, performance issues, or before claiming work complete. Prevents random fixes, masks over symptoms, and false completion claims.
memory-leak-debugging
morningstar0709/trae-agent-system
Diagnose JavaScript, browser, and Node.js memory leaks in Trae with Chrome DevTools MCP and memlab-oriented workflows. Use when the user reports high memory usage, OOM errors, heap snapshots, detached DOM nodes, growing memory, or Chinese requests such as 内存泄漏, 内存占用高, 页面越用越卡, 分析 heapsnapshot, or 排查 Node 内存问题.
debug-memory-profiler
lgrappag/workflows-agents
Profile memory usage to identify leaks and inefficiencies
debug
jcchikikomori/skills-md
Debugs production issues by reproducing bugs, running 5 Whys root cause analysis, and writing verifying test cases. Use when investigating a bug or production incident.
devops-troubleshooter
jiho00seo-dev/antigravity-awsome-skill
Expert DevOps troubleshooter specializing in rapid incident
log-analysis
apgamerinfo/boyser-ai
ไล่ log หา error/pattern/สาเหตุ ใช้เมื่อผู้ใช้ขอวิเคราะห์ log หาว่าเกิดอะไรขึ้น หรือ debug จากไฟล์ log
agent-customization
microsoft/vscode
**WORKFLOW SKILL** — Create, update, review, fix, or debug VS Code agent customization files (.instructions.md, .prompt.md, .agent.md, SKILL.md, copilot-instructions.md, AGENTS.md). USE FOR: saving coding preferences; troubleshooting why instructions/skills/agents are ignored or not invoked; configuring applyTo patterns; defining tool restrictions; creating custom agent modes or specialized workflows; packaging domain knowledge; fixing YAML frontmatter syntax. DO NOT USE FOR: general coding questions (use default agent); runtime debugging or error diagnosis; MCP server configuration (use MCP docs directly); VS Code extension development. INVOKES: file system tools (read/write customization files), ask-questions tool (interview user for requirements), subagents for codebase exploration. FOR SINGLE OPERATIONS: For quick YAML frontmatter fixes or creating a single file from a known pattern, edit the file directly — no skill needed.
project-setup-info-local
microsoft/vscode
Comprehensive setup steps to help the user create complete project structures in a VS Code workspace; this tool is designed for full project initialization and scaffolding, not for creating individual files. When to use this tool: user wants to create a new complete project from scratch; setting up entire project frameworks (TypeScript projects, React apps, Node.js servers, etc.); initializing Model Context Protocol (MCP) servers with full structure; creating VS Code extensions with proper scaffolding; setting up Next.js, Vite, or other framework-based projects; user asks for "new project", "create a workspace", "set up a [framework] project"; need to establish a complete development environment with dependencies, config files, and folder structure. When NOT to use this tool: creating single files or small code snippets; adding individual files to existing projects; making modifications to existing codebases; user asks to "create a file" or "add a component"; simple code examples or demonstrations; debugging or fixing existing code. This tool provides complete project setup including: folder structure creation; package.json and dependency management; configuration files (tsconfig, eslint, etc.); initial boilerplate code; development environment setup; build and run instructions. Use other file creation tools for individual files within existing projects.
temporal-developer
temporalio/claude-temporal-plugin
Develop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET, Ruby, and Rust. Use when the user is building workflows, activities, or workers with a Temporal SDK, debugging issues like non-determinism errors, stuck workflows, or activity retries, using Temporal CLI, Temporal Server, or Temporal Cloud, or working with durable execution concepts like signals, queries, heartbeats, versioning, continue-as-new, child workflows, or saga patterns. Also use when the user mentions "run a Temporal workflow from the CLI", "start a dev server", "run temporal server start-dev", "temporal workflow start", "temporal workflow execute", "temporal workflow signal", "temporal workflow query", "temporal workflow update".