root-cause
Use when something is broken and the cause isn't known. Runs prompts/investigate.md — reproduce the reported case, confirm a baseline, test hypotheses one at a time, fix the root cause, find sibling occurrences.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- root-cause
- metadata
- { "argument-hint": "<symptom, where it was seen, expected vs actual>" }
- description
- Use when something is broken and the cause isn't known. Runs prompts/investigate.md — reproduce the reported case, confirm a baseline, test hypotheses one at a time, fix the root cause, find sibling occurrences.
03 SKILL.md 正文
Run the defect investigation exactly as written in prompts/investigate.md. Read that file
in full first; it is the authoritative instruction set, and this skill only wires it up.
- Assemble the inputs from what was given with the request. Map them onto the prompt's inputs (symptom, where, expected vs actual, since when). If the symptom or where it was seen is missing, ask for both in one question before starting.
- Execute the phases in order. Don't touch code before Phase 0 has a reproduction of the reported case.
- Report using the prompt's "Output of this prompt" contract.
04 同仓库更多 Skills
verify
Use when a change is about to be committed, or someone asks to verify one. Runs prompts/verify.md — the repo's fast checks (lint, typecheck, the tests the change touches, generated files rebuilt) on the tree being committed, saying what passed, what failed, and what wasn't run.
template-update
Use when this repository should take a release of the template it was built from, or a template update pull request needs finishing. Runs prompts/template-update.md — finds the template version it has, reads the CHANGELOG to the release, brings the process files across, merges each parked .template, and does what the release's entries ask.
root-cause
Use when something is broken and the cause isn't known. Runs prompts/investigate.md — reproduce the reported case, confirm a baseline, test hypotheses one at a time, fix the root cause, find sibling occurrences.
review-change
Use when someone asks for a review, a critical or hard look, or a second opinion on a change before it merges, whether a PR, a branch, a diff range, or a pasted diff. Runs prompts/review.md — an adversarial, evidence-cited review, including the "passes its own tests" failures.
pre-pr
Use when a change is ready to leave your hands — before opening or updating a pull request. Runs prompts/pre-pr.md — merge the base, run the full gate, prove new checks can fail, self-review, sweep docs, and draft the description.
plan-change
Use when someone asks to plan a feature, a fix, or a refactor before it's built, or a change is too large to start on directly. Runs prompts/plan-change.md — sizes the change and stops for a small one; otherwise writes docs/changes/<date>-<slug>.md against docs/product.md, AGENTS.md, and the ADRs, with behavior, design, risks, and tasks that each name their test.