five-whys
Finds the root cause of a bug, failure or recurring problem by asking "why" until the answer is a cause you can fix. Use when the user asks why something keeps happening, or wants the root cause rather than a quick fix.
- License 许可
- NOASSERTION
- 最近更新
- 2026-11-11
- Stars
- ★ 3.7k
- Forks
- 417
01 前言 Front Matter
- name
- five-whys
- description
- Finds the root cause of a bug, failure or recurring problem by asking "why" until the answer is a cause you can fix. Use when the user asks why something keeps happening, or wants the root cause rather than a quick fix.
- argument-hint
- [problem]
03 SKILL.md 正文
Find the root cause of this problem: $ARGUMENTS
If no problem is given, ask for one in a single sentence, then stop.
- Restate the problem as a symptom someone can observe: what happens, where and when.
- Ask "Why does this happen?" Answer from evidence: the code, tests, logs and git history. Mark any answer you can't back with evidence as a guess.
- Ask "Why?" of that answer, and keep going until the answer is a cause the team can change. That often takes about five rounds; stop sooner if you get there, and say so if you need more.
- Check the chain backwards: each cause must explain the step before it.
- Report the chain as a numbered list, the root cause in one sentence, then one fix for the root cause and one for the symptom.
Don't change any files. Propose the fixes and let the user decide.
04 同仓库更多 Skills
check-links
Runs the link checker on a folder and explains each broken link it finds, with the file, the line and a likely fix. Use when someone asks to check links or find broken links in the docs.
changelog
Adds a one-line entry for the staged changes to CHANGELOG.md. Use when the user asks for a changelog entry.
tdd
Builds a requested feature test-first, one behavior at a time, and stops at a diff for review. Use when the user asks for a new function or feature, or says test-first or TDD.
team-review
The team's review of a change to linkcheck, run the same way on a laptop and in CI. Use on a staged diff or a pull request.
review-checklist
The team's checklist for reviewing a change to linkcheck. Use before you commit or open a pull request.
onboard
Explains this repository's shared Claude Code setup to a new teammate, covering what is committed and shared, what stays personal, and what the team-kit plugin adds. Use when someone asks how the team's Claude Code setup works or what they get by cloning the repository.