Ponytail Debt

by dietrichgebertb088b2df6e08MITListed Oct 8, 2026Updated Oct 8, 2026

Harvest every ponytail: shortcut comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.

Instructions onlySoftware Development
AI-generated overview

Scans a repository for ponytail: shortcut comments and compiles them into a single debt ledger report.

What it does
Searches the codebase for comment markers of the form ponytail: using a grep command that skips node_modules, .git, and build output. Each hit becomes a ledger row grouped by file, listing the file and line, what was simplified, the named ceiling, and the upgrade trigger. Comments that name no upgrade path or trigger are tagged no-trigger, and the report ends with a count of markers and untriggered ones. It reads and reports only; on request it can write the ledger to a file such as PONYTAIL-DEBT.md.
When to use it
Use it when you want to collect deliberate shortcuts and deferrals scattered across a codebase so they are tracked rather than forgotten. It suits a one-shot audit of technical debt markers before or after a development cycle.
Requirements
Requires a repository containing ponytail: comment markers and a shell environment with grep available. No scripts ship with the skill; it is instructions only. Writing the ledger to a file is optional and only on request.

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.

Scan

Grep the repo for comment markers, skipping node_modules, .git, and build output:

grep -rnE --exclude-dir=.git --exclude-dir=node_modules --exclude-dir=dist --exclude-dir=build '(#|//|/[*]) ?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.

Output

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.

Boundaries

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.

Source and attribution

Source:dietrichgebert/ponytailin.openclaw/skills/ponytail-debtat commitb088b2d

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal