diff options
| author | Craig Jennings <c@cjennings.net> | 2026-04-22 08:08:59 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-04-22 08:08:59 -0500 |
| commit | 1fb4232671d30aa867e3e7b0c74d48a989e460c5 (patch) | |
| tree | bbe7ccaa14c1ca2a7e4b7c7378104074dbd1a8ea /debug | |
| parent | 5302673fab3ade9a348dd096aafe12fe21310ff6 (diff) | |
| download | rulesets-1fb4232671d30aa867e3e7b0c74d48a989e460c5.tar.gz rulesets-1fb4232671d30aa867e3e7b0c74d48a989e460c5.zip | |
chore: remove fix-issue skill, superseded by start-work
The fix-issue skill has been replaced by start-work, which covers the same ground (picking up a ticket with a known fix and carrying it through to handoff) with a seven-phase structure and three user-approval gates. Deleted fix-issue/SKILL.md and swept the references.
Updated:
- Makefile SKILLS list: remove fix-issue, add start-work so make install creates the right symlink.
- brainstorm/SKILL.md: implementation-path list points at start-work.
- debug/SKILL.md description: both "do NOT use for ticket-driven work" and "Companion to" references updated.
- review-code/SKILL.md description: "drafting implementation" redirect updated.
No change in meaning. Every old fix-issue context now names start-work.
Diffstat (limited to 'debug')
| -rw-r--r-- | debug/SKILL.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/debug/SKILL.md b/debug/SKILL.md index 7b207aa..1a64e82 100644 --- a/debug/SKILL.md +++ b/debug/SKILL.md @@ -1,6 +1,6 @@ --- name: debug -description: Investigate a bug or test failure methodically through four phases — understand the symptom (reproduce, read logs, locate failure point, trace data flow), isolate variables (minimal repro, bisect), form and test hypotheses, then fix at the root. Captures evidence before proposing fixes; rejects shotgun debugging; escalates to architectural investigation after three failed fix attempts. Use when the failure mode is unclear, the failure reproduces inconsistently, or you're about to start guessing. Do NOT use for clear local bugs where the fix site is obvious (just fix it), for ticket-driven implementation work with a known fix (use fix-issue), for backward-walking a specific error up the call stack (use root-cause-trace), or for process/organizational root-cause analysis of recurring incidents (use five-whys). Companion to fix-issue / root-cause-trace / five-whys — debug is the broad investigative workflow; the others specialize. +description: Investigate a bug or test failure methodically through four phases — understand the symptom (reproduce, read logs, locate failure point, trace data flow), isolate variables (minimal repro, bisect), form and test hypotheses, then fix at the root. Captures evidence before proposing fixes; rejects shotgun debugging; escalates to architectural investigation after three failed fix attempts. Use when the failure mode is unclear, the failure reproduces inconsistently, or you're about to start guessing. Do NOT use for clear local bugs where the fix site is obvious (just fix it), for ticket-driven implementation work with a known fix (use start-work), for backward-walking a specific error up the call stack (use root-cause-trace), or for process/organizational root-cause analysis of recurring incidents (use five-whys). Companion to start-work / root-cause-trace / five-whys — debug is the broad investigative workflow; the others specialize. --- # /debug — Systematic Debugging |