菜单
Ponytail review, audit, and debt workflows for over-engineering review and shortcut ledger scans. Use for /ponytail review, /ponytail audit, /ponytail debt, or when asked what to delete, simplify, or track as ponytail debt.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Authenticated browser QA on the Voyager dev server — mint real AuthKit sessions for seeded test personas via /api/dev/login, then drive the UI with Playwright. Use whenever QA, visual review, or E2E verification needs a logged-in user.
Orchestrate parallel work across worker agents in herdr panes (omp by default; fable/claude workers on explicit user request) — spawn or discover workers, dispatch assignment packets, monitor liveness, and verify results before committing. Use whenever a code change should be delegated instead of implemented firsthand (delegation-first policy), e.g. /herdr-orchestrate 3 to spawn three workers, or /herdr-orchestrate p17,p18,p19 to use existing panes.
Observe Herdr peers safely with native read-only herdr commands.
Initialize or repair AOC context, memory, and tasks safely.
Anime.js v4 API correctness, imports, targeting, value mapping, refresh/revert semantics, and sane implementation defaults. Use when writing or fixing Anime.js code.
Audit Anime.js work for performance, reduced-motion behavior, engine settings, scroll readability, SVG costs, and cleanup discipline.
| name | ponytail-workflows |
| description | Ponytail review, audit, and debt workflows for over-engineering review and shortcut ledger scans. Use for /ponytail review, /ponytail audit, /ponytail debt, or when asked what to delete, simplify, or track as ponytail debt. |
Ported from DietrichGebert/ponytail, MIT licensed: https://github.com/DietrichGebert/ponytail
Review diffs for unnecessary complexity. One line per finding: location, what to cut, what replaces it. The diff's best outcome is getting shorter.
L<line>: <tag> <what>. <replacement>.
Use <file>:L<line>: ... for multi-file diffs.
Tags:
delete: dead code, unused flexibility, speculative feature. Replacement: nothing.stdlib: hand-rolled thing the standard library ships. Name the function.native: dependency or code doing what the platform already does. Name the feature.yagni: abstraction with one implementation, config nobody sets, layer with one caller.shrink: same logic, fewer lines. Show the shorter form.Bad: "This EmailValidator class might be more complex than necessary, have you considered whether all these validation rules are needed?"
Good: L12-38: stdlib: 27-line validator class. "@" in email, 1 line; real validation is the confirmation mail.
Good: L4: native: moment.js imported for one format call. Intl.DateTimeFormat, 0 deps.
Good: repo.py:L88: yagni: AbstractRepository with one implementation. Inline it until a second exists.
Good: L52-71: delete: retry wrapper around an idempotent local call. Nothing replaces it.
Good: L30-44: shrink: manual loop builds dict. dict(zip(keys, values)), 1 line.
End with the only metric that matters: net: -<N> lines possible.
If there is nothing to cut, say Lean already. Ship. and stop.
Run a repo-wide ponytail review. Scan the tree, rank findings biggest cut first, and apply nothing.
delete: dead code, unused flexibility, speculative feature. Replacement: nothing.stdlib: hand-rolled thing the standard library ships. Name the function.native: dependency or code doing what the platform already does. Name the feature.yagni: abstraction with one implementation, config nobody sets, layer with one caller.shrink: same logic, fewer lines. Show the shorter form.Look for:
One line per finding, ranked:
<tag> <what to cut>. <replacement>. [path]
End with net: -<N> lines, -<M> deps possible.
Nothing to cut: Lean already. Ship.
Every deliberate ponytail shortcut should be marked with a ponytail: comment naming its ceiling and upgrade path. This command collects them into a ledger so a deferral cannot quietly become permanent.
Search the repo for comment markers, skipping .git, dependencies, and build output. Use the repository's search tools, not shell grep, when operating inside OMP.
Match comment prefixes such as:
// ponytail:# ponytail:/* ponytail:<!-- ponytail:Each hit is one ledger row. The comment prefix keeps prose that merely mentions the convention out of the ledger.
One row per marker, grouped by file:
<file>:<line> — <what was simplified>. ceiling: <named limit>. upgrade: <trigger to revisit>.
Convention: ponytail: <ceiling>, <upgrade path>.
Flag any marker without a concrete upgrade path or trigger as no-trigger; those are the ones that rot.
End with <N> markers, <M> with no trigger.
Nothing found: No ponytail: debt. Clean ledger.