wangjunxiao/ponytail
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix scope ambiguity in ponytail-audit and ponytail-review Boundaries (#163)

Browse Source 
The Boundaries line opened with "Complexity only, correctness bugs, security
holes, and performance go to a normal review pass." The comma after "Complexity
only" fuses the in-scope item with the out-of-scope list, so a model parsing it
literally can read all four categories as targets of the audit — the opposite of
intent.

Restate the boundary as an explicit scope fence: name what is in scope, then
mark correctness/security/performance as explicitly out of scope. "Out of scope"
is phrasing models reliably honor as a constraint. Also aligns the scope term
with each skill's stated purpose (over-engineering).

Applied to both skills/ and the .openclaw/ mirror so the two trees stay in sync.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Arthur Morrill
2026-06-19 00:26:33 +02:00
committed by GitHub
co-authored by Claude Opus 4.8
parent 83f67a261a
commit b0c5820bb1
4 changed files with 12 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/ponytail-review/SKILL.md
+3 -2
View File
@@ -49,8 +49,9 @@ If there is nothing to cut, say `Lean already. Ship.` and stop.
## Boundaries
Complexity only, correctness bugs, security holes, and performance go to a
normal review pass, not this one. A single smoke test or `assert`-based
Scope: over-engineering and complexity only. Correctness bugs, security holes,
and performance are explicitly out of scope — route them to a normal review
pass, not this one. A single smoke test or `assert`-based
self-check is the ponytail minimum, not bloat, never flag it for deletion.
Does not apply the fixes, only lists them.
"stop ponytail-review" or "normal mode": revert to verbose review style.