mirror of
https://github.com/cursor/plugins.git
synced 2026-09-14 20:00:00 +08:00
lauren
e8d856f027
* docs(pstack): port the September skill audit cuts from the internal tree Port of the 2026-09-01 to 2026-09-07 audit program on the internal skill tree. Deletion-only density cuts and the mannered prose pass applied wherever the OSS sentence is the same sentence. Two new principle leaves, Attack the Premise and Test Behavior Not Implementation, with their index lines. Critique mode removed from how and its callers. PR-body briefing rules in opening-a-pr and technical-writing. Model pins stay on the setup-pstack role mechanism. No internal path, slug, or name added. * docs(pstack): restore the autopilot chooser rule that multi-phase-plan cites multi-phase-plan step 4 picks between autopilot-full and autopilot-stack "per the rule at the end of playbooks/autopilot-stack.md". The density pass removed that paragraph and left the pointer dangling. Restore the paragraph verbatim. The chooser is a rule, not a restatement, and no other file states it. Addresses the Bugbot finding on PR #329. --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com>
1.2 KiB
1.2 KiB
name, description, disable-model-invocation
| name | description | disable-model-invocation |
|---|---|---|
| principle-fix-root-causes | Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes. | true |
Fix Root Causes
When debugging, do not fix symptoms. Trace every problem to its root cause and fix it there.
Why: Symptom fixes accumulate. Each workaround makes the system harder to reason about, and the real bug remains. Root-cause fixes are slower upfront but reduce total debugging time.
Pattern:
- Reproduce first
- Ask "why" until you hit the root cause
- Do not add guards (adding a nil check to silence a crash is a symptom fix)
- If a workaround needs a paragraph-long comment to justify it, the code is wrong (fix the code, not the comment)
- Check for the pattern, not just the instance (grep for the same pattern, fix all instances)
- When stuck, instrument. Don't guess (add logging, read the actual error)
Restart bugs: suspect state before code
When something "fails after restart," suspect stale persistent state first: config files, caches, lock files, serialized state. If clearing a state file restores behavior, prioritize state validation as the fix.