В каталоге 183 730 навыков в 14 категориях.
Root-cause debugging for runtime errors, failing tests, regressions, and unexpected behavior. Use when you need to isola...
Systematic root-cause debugging — reproduce, isolate, hypothesize, fix with TDD. Use when: bug, error, fix, broken, cras...
Conventions and tools for the `debug` npm package. Run tests with debug output.
Investigate-then-decide root-cause analysis for a defect whose cause is unknown (distinct from /fix, which assumes a kno...
Use when investigating unexpected behavior, test failures, runtime errors, or regressions. Systematic 4-phase diagnosis:...
Find and fix the root cause of a bug, not the symptom.
Trace and diagnose runtime bugs with evidence. Use when something isn't working but code looks correct, when you need to...
Standard workflow for debugging tasks. Use when something is broken, an error occurs, or behavior is unexpected. Finds r...
Investigation-first debugging — gather evidence, form confirmed root-cause hypothesis, hand off to fix mode with diagnos...
Root cause analysis for bugs and errors. Use when something is broken and the cause is not obvious. Applies the 5-step i...
Triage and diagnose production or local issues by following logs → traces → metrics (HTTP/gRPC/async). Use when investig...
Investigate root causes systematically using scientific method
A check fails or behavior is wrong and the cause isn't obvious — reproduce, isolate the root cause, fix narrowly, and pr...
Systematic debugging with persistent state across context resets
Systematically diagnose and fix errors, test failures, and unexpected behavior.
debug this, fix this bug, why is this failing, investigate error, trace the issue, something is broken, test failure, sy...
Use when the user reports an error, unexpected behavior, test failure, or asks to trace or diagnose a problem. Applies 6...
Systematic debugging workflow: reproduce, isolate, fix, verify
Use for bugs, unexpected behavior, regressions, or failing tests you did not write.
Debug errors, find root causes, and fix failing code.
Use when a user reports a bug, error, or unexpected behavior and wants it troubleshot and fixed. Interactive: grills the...
Browser debugging with agent-browser CLI. Use when: - User mentions "screenshot", "visual bug", "inspect element" - User...
Systematic 4-phase debugging. NO fixes without root cause investigation first. Prevents thrashing and random guessing.
Systematic debugging with structured reproduction and root cause analysis.
Fix bugs systematically instead of guessing. Use when features break, users report errors, or tests fail. Covers reprodu...
Fixes a bug test-first, or tests a hypothesis without fixing. Use when the user reports a bug, error, failing test or st...
[Fix & Debug] Systematic debugging with root cause investigation. Use when bugfix workflow reaches debug step.
Usar al investigar un bug o error en la aplicación
Systematic bug investigation and resolution workflow with root cause analysis.
Use when encountering bugs, test failures, or unexpected behavior. Systematic root cause investigation and bug fixing be...
Use when something is broken — a failing or flaky test, crash, wrong result or regression — and the root cause must be r...
Systematic debugging methodology with binary search, observability, and root cause analysis
Debug FalkorDB crashes, hangs, panics, and incorrect query results - attach lldb/gdb to redis-server with the module loa...
Systematically reproduce, isolate, fix, and verify bugs and failing tests. Use when the user reports a bug, error, stack...
Structured bug diagnosis and fixing workflow that reproduces, diagnoses root cause, applies a minimal fix, writes regres...
Hypothesis-driven debugging through observe, hypothesize, test, narrow. Use when something is wrong and you need to find...
Investigate a problem, log it to the debug changelog, cross-check past issues, and suggest a non-duplicate fix
Structured bug diagnosis and fixing workflow — reproduce, diagnose root cause, apply minimal fix, write regression test,...
Structured bug diagnosis and fix — Root cause analysis, pattern scanning, regression tests
Unified testing, debugging, and error-fixing skill for backend, database, and frontend. Use when investigating bugs, run...
Discipline skill — systematic debugging process. Use when encountering any bug, debug issue, test failure, broken functi...
系统化排错：以运行时证据走"复现 → 假设 → 验证 → 定位 → 修复 → 回归"闭环，排查报错、测试失败、行为异常。触发："排查这个 bug"、"debug 一下"、"为什么会报错"、"定位一下问题"、"这个测试为什么挂了"，或被 ap...
Debug systematically with root cause analysis before fixes. Use for bugs, test failures, unexpected behavior, performanc...
Debugging command. Activates DEBUG mode for systematic problem investigation.
Systematic stop-the-line root-cause debugging for deterministic failures with a clear signal: a failing test, broken bui...
Investigate and fix bugs, failing tests, regressions, build failures, or unexpected behavior using boundary localization...
Systematic bug fixing — reproduce, localise with logs/tests/diagnostics, form and test a hypothesis, fix the root cause,...
Use when a test fails, a build breaks, a bug is reported, behaviour is unexpected, performance drops, or an integration...
Use when diagnosing a Python traceback, failing test, intermittent failure, integration defect, or other unexpected runt...
Use when facing a bug, test failure, or unexpected behavior that isn't immediately obvious
Systematic root cause analysis. Reproduce, isolate, fix, verify, prevent. Use when: "debug this", "why is this broken",...
Use when encountering any bug, test failure, build break, or unexpected behavior — runs a 4-phase systematic debugging p...
(ePost) Use when user says "debug", "trace this", "diagnose", "it crashes", "why is this failing", or provides a stack t...
Systematic 4-phase debugging protocol — REPRODUCE → ISOLATE → HYPOTHESIZE → VERIFY before any fix is written. Forces roo...
Systematic root-cause analysis for bugs, errors, and unexpected behavior
Find out why something fails locally, in CI or in a deployed environment. Use when the user reports an error, a failing...
Hypothesis-driven debugging — architecture-first reading + evidence-before-fix. For bugs that resisted naïve fix attempt...
Debug issues using systematic investigation
Debug runtime-dependent bugs by generating competing hypotheses, adding temporary structured-log probes, collecting loca...
v1.0.1 — When software is reported broken, read its logs before diagnosing it. Start with the repository .log/ directory...
Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "thi...
Find and fix the root cause of a bug through a disciplined reproduce-first diagnosis loop, with browser escalation where...
Systematic debugging using hypothesis-driven investigation with test, narrow, and resolve loops
Structured platform troubleshooting — classifies the problem layer, collects evidence, forms a root-cause hypothesis, an...
Troubleshoot and debug issues. Use when the user reports an error, a test failure, unexpected behavior, or asks to inves...
Hypothesis-driven defect isolation — stack-trace forensics, breakpoint strategy, state inspection, and root-cause confir...
Debug a problem in claude-desktop-extra by pulling the right local evidence - the most recent local-agent-mode session t...
Systematic debugging workflow for tracking down and fixing issues. Use when encountering bugs, errors, or unexpected beh...
Debug a specific issue by reading logs and investigating code
Debug a bug or unexpected behavior systematically. Use when the user says "there's a bug", "this isn't working", "I'm ge...
Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs f...
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports som...
Root cause analysis for bugs and unexpected behavior. Traces errors through code, uses structured reasoning, and hands o...
Investigate a failure, regression or incorrect result in an integration or application, even before it can be reproduced...
Use when a bug, an unexpected test failure or a repeated error shows up during the code step, trace the cause backwards...
Use when encountering any bug, test failure, or unexpected behavior — enforces root cause investigation before fixes. Pr...
Debug errors, bugs, and unexpected behavior systematically in Home Assistant integration. Use when investigating errors,...
Root cause debugging before fixes. Use when investigating bugs, diagnosing test failures, troubleshooting unexpected beh...
Systematic bug diagnosis — reproduce, isolate, hypothesize, verify, fix. Usage: /debug [what's broken]
Debug issues by investigating logs, database state, and git history
Systematically debugs issues using structured diagnosis — reproduce, isolate, identify root cause, and fix. Use when fac...
Instrument web/web-app code with structured debug logging via a global variable (window.__debug_logs). Produces a clean...
Systematic debugging with MCP integration, auto-invoke from qa-commit, Phase 7 Harden
Track your job applications
Investigate and fix a bug systematically
Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law:...
Debug a failing test or build error in WooCommerce iOS
Systematic debugging methods, log analysis, and performance diagnostics. Use when debugging issues, analyzing errors, or...
系統性 debug 工作流：捕捉錯誤、分析日誌、關聯跨系統 pattern，產出有根因與修復驗證的報告。適用於 bug、test 失敗、生產異常。
Identifies bugs, analyzes errors, performs root cause analysis, and proposes fixes
Systematically debug issues using graph-powered code navigation
Debug your application to find and fix a bug
A strict, scientific debugging protocol (The "Iron Law"). No fixes allowed without root cause investigation.
v0.1.0 — When software is reported broken, read its logs before diagnosing it. Start with the repository .log/ directory...
GitHub Actions のワークフロー実行エラーを調査し、原因を特定して解決策を提案する。「Actions エラー」「ワークフロー失敗」「CI が落ちた」「ビルド失敗」「テスト失敗」「Actions を調べて」「CI のエラーを見て」...
Depurar o agente IA com metodologia
Systematic evidence-based debugging using runtime logs. Generates hypotheses, instruments code with NDJSON logs, guides...
Debug 场景特化。触发条件：用户说"帮我 debug"、"这代码炸了"、"报错了"、贴 stack trace、贴报错截图。 提供：动手前检查清单、修改纪律、退出条件判断、debug 三板斧方法论。
Use this to diagnose WHY an LLM agent or chain produced a wrong, empty, slow, or expensive result, by reading its observ...