From praxis-workflow
Harvests every `ponytail:` comment into a debt ledger, tracking deliberate shortcuts. One-shot report, no changes. Activate via 'ponytail debt' or '/ponytail-debt'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/praxis-workflow:ponytail-debtThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Every deliberate ponytail shortcut is marked with a `ponytail:` comment naming
Every deliberate ponytail shortcut is marked with a ponytail: comment naming
its ceiling and upgrade path. This collects them into one ledger so a deferral
can't quietly become permanent.
Grep the repo for comment markers, skipping node_modules, .git, and build
output:
grep -rnE '(#|//) ?ponytail:' . (add other comment prefixes if your stack uses them)
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: <the limit named>. upgrade: <the trigger to revisit>.
The convention is ponytail: <ceiling>, <upgrade path>, so pull the ceiling
and the trigger straight from the comment. Want an owner per row too? add
git blame -L<line>,<line>.
Flag the rot risk: any ponytail: comment that names no upgrade path or
trigger gets a no-trigger tag, those are the ones that silently rot.
End with <N> markers, <M> with no trigger. Nothing found: No ponytail: debt. Clean ledger.
Reads and reports only, changes nothing. To persist it, ask and it writes the
ledger to a file (e.g. PONYTAIL-DEBT.md). One-shot. "stop ponytail-debt" or
"normal mode" to revert.
npx claudepluginhub faustofanb/praxis --plugin praxis-workflow12plugins reuse this skill
First indexed Jun 19, 2026
Showing the 6 earliest of 12 plugins
Harvests every `ponytail:` comment into a debt ledger, tracking deliberate shortcuts. One-shot report, no changes. Activate via 'ponytail debt' or '/ponytail-debt'.
Identifies, categorizes, and prioritizes technical debt across seven dimensions with remediation plans and effort estimates. Useful for refactoring track planning.
Find where the debt actually hurts. Ranks files by churn x complexity from git history to surface the real hotspots, then plans behavior-preserving refactors for the worst offenders.