AGENT SKILL

principle-fix-root-causes

Fix root causes. Apply when debugging a failure or repairing a finding.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 2
Forks
0

01 前言 Front Matter

name
principle-fix-root-causes
license
MIT
metadata
{ "source": "pstack principle-fix-root-causes, MIT, Copyright (c) 2026 Lauren Tan, github.com/cursor/plugins, adapted; checked against pstack 0.15.36 at commit 0bb6f37" }
description
Fix root causes. Apply when debugging a failure or repairing a finding.

03 SKILL.md 正文

<!-- Generated by scripts/build.mjs from the sources; edit the source, then run npm run build. -->

Fix root causes

Fix the fault where it started, not where it surfaced. The root cause is where the system first did something wrong, or missed a state that it should handle.

Why. A symptom fix hides the evidence, and the fault surfaces again elsewhere.

What to do.

  • Reproduce first.
  • Ask "why" until the answer is a wrong decision in the code, not a consequence of an earlier one.
  • Ask whether the state is legitimate. If it may occur, handle it in the code that broke on it. If not, a guard, retry, swallowed error, clamped value or discarded state there hides the bug: find what made the state.
  • A workaround that needs a paragraph to justify it means the code is wrong.
  • Fix every instance of the same shape.
  • When stuck, measure: add logging, read the actual error and state.
  • If the deciding fact was hard to find, propose a cheap, always-on signal that would have shown it at once.

After a restart, suspect stale persistent state before code: configuration files, caches, lock files, serialised state.

Stop when the reproduction no longer fails for the reason you found, not when the symptom is hidden.

04 同仓库更多 Skills

erickb336
erickb336/sage-stack

writing-standard

Write at 80% of Simplified Technical English. Apply to any text an agent writes for a person: messages, reports, specs, findings, reviews, plans.

★ 2
erickb336
erickb336/sage-stack

sage

The state tool of sage mode: records tasks, routes, agent runs, findings, verdicts by head SHA and the user's gates in ~/.claude/sage/<project>/. Use in sage mode for every change of a task's state, and before any merge. Claude Code only.

★ 2
erickb336
erickb336/sage-stack

sage-help

Help with sage: how to set it up, switch sage mode and autopilot, read the board, answer the chief's questions, pick a skill or a principle, fix a run that went wrong, and find where sage keeps its files. The user types /sage:sage-help (or /sage-help) with a question. Load it only when the user types it; do not load it on your own. Claude Code only.

★ 2
erickb336
erickb336/sage-stack

report

The report that every sage agent ends with: STATUS, RESULT, EVIDENCE, FINDINGS, QUESTIONS, NOT VERIFIED, BRANCH. Use at the end of any task that the sage chief of staff gave you. Claude Code only.

★ 2
erickb336
erickb336/sage-stack

remote-control

Set up Remote Control, so that the user can follow, steer and start Claude Code sessions from the Claude app on a phone. It turns Remote Control on for every new session, and it can run a server in a folder (such as ~/workspace) that starts at each login. Use when the user asks to reach sessions or start new ones from a phone, or to set up, check or undo Remote Control. Claude Code only.

★ 2
erickb336
erickb336/sage-stack

readme-guide

Write a project README. Apply when you write, change or review a README of any project, in any language.

★ 2