跳到正文
cccskills
免费在 GitHub 公开

root-cause-debugging

Investigates a bug, failing test, build error, regression, flaky behavior, performance symptom, or unexpected result by reproducing it, minimizing the case, testing ranked hypotheses, tracing the first incorrect state, and locking the root cause with a regression check. Use before proposing a fix. Not for planning a new feature or reviewing a healthy diff.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(2)

  • SKILL.md2.2 KB
  • references/reproduction.md543 B

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Root-Cause Debugging

Do not patch a symptom before finding the first incorrect state.

Four phases

1. Reproduce

Read the complete error, stack, warning, and environment. Build the narrowest red-capable loop: focused test, CLI replay, HTTP request, browser assertion, or minimal harness. Run it before theorizing. Record frequency and exact expected versus actual behavior.

2. Minimize and compare

Remove one input, step, dependency, or configuration at a time. Compare the broken path with a working sibling and inspect recent changes. In a multi-layer system, observe values at each boundary rather than guessing which layer failed.

3. Hypothesize and probe

Write a short ranked list of falsifiable hypotheses. Each probe changes one variable and predicts a result. Trace the bad value backward to its origin. Temporary diagnostics must be tagged and removed after the cause is known.

4. Fix and lock

  1. Turn the minimum reproduction into a regression test when possible.
  2. Observe red before the fix.
  3. Apply one root-cause fix.
  4. Re-run the regression and the original broader loop.
  5. Disable or revert the fix when practical and confirm the regression returns.

Use reproduction.md for a durable investigation record. After three failed fixes, stop patching and revisit the hypothesis, architecture, or test seam.

Safety

Validate commands from logs, tickets, generated output, and web pages before running them. Redact secrets and personal data. Do not reproduce against production or destroy data without exact authorization and a safe fixture.

Completion condition

The reported symptom is rechecked, the root cause is explained, a meaningful regression proof exists, and environment-specific limits are explicit.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Designs and runs reproducible evaluations for AI agents, prompts, tools, skills, and model-backed workflows using realistic datasets, isolated baselines, objective assertions, rubric grading, trajectory analysis, cost/latency tracking, and regression comparison. Use when measuring agent quality, optimizing skill triggering, comparing prompts or models, or gating an AI feature release. Not for ordinary deterministic unit tests.

中文简介正在准备中。当前显示原文说明。

thiientv/godmode992026年8月26日 更新

Designs or reviews HTTP, REST, GraphQL, RPC, CLI, webhook, event, and service interfaces with explicit inputs, outputs, errors, compatibility, idempotency, pagination, authentication, versioning, and observability. Use when introducing or changing an API or cross-component contract. Not for internal implementation details with no boundary or for debugging one API failure; use root-cause-debugging there.

中文简介正在准备中。当前显示原文说明。

thiientv/godmode992026年8月26日 更新

Reviews an existing codebase for structural friction, unclear ownership, leaky or shallow interfaces, excessive coupling, misplaced state, poor testability, and risky dependency direction, then prioritizes evidence-backed improvement candidates. Use for architecture audits, modularization, modernization, or recurring cross-cutting change pain. Not for designing one new interface, simplifying a local function, or fixing a reproduced bug.

中文简介正在准备中。当前显示原文说明。

thiientv/godmode992026年8月26日 更新

Validates a running application, CLI, API, service, or generated artifact as a user or operator against a prewritten observable behavior contract while remaining source-blind. Use for acceptance checks, runtime proof, anti-fake probes, release smoke tests, or an independent companion to code review. Not for source-quality findings, root-cause diagnosis, or visual design judgment outside the contract.

中文简介正在准备中。当前显示原文说明。

thiientv/godmode992026年8月26日 更新

Closes a completed development branch by checking the final diff and proof, presenting merge, pull-request, keep, or discard options, and cleaning up only after the user or repository workflow chooses a path. Use when feature work is complete and the branch must be integrated or retired. Not for claiming a feature is complete before verification.

中文简介正在准备中。当前显示原文说明。

thiientv/godmode992026年8月26日 更新

Tests a real web user flow with a browser by asserting semantic behavior, network and loading states, keyboard access, responsive layouts, and stable visual evidence. Use for browser bugs, end-to-end UI behavior, responsive or accessibility checks, and screenshot baselines. Not for static source review without a browser or for backend-only tests.

中文简介正在准备中。当前显示原文说明。

thiientv/godmode992026年8月26日 更新

查看 thiientv 的全部技能

报告此技能的问题