ponytail-debt is agent-read markdown (skill) from kunolu/640-skills: Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail ledger", or "what did we mark to do later". One-shot report, changes nothing..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
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 '(#|//) ?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
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_qo67qaqnmucpozrl
GET https://markdownregistry.com/api/v1/resolve?ref=kunolu/640-skills/ponytail-debt
GET https://markdownregistry.com/api/v1/blob/c84fba75f0ca12bfe83f9a78ea02fd125c5dd3f1fbb18124105a489937f284e6
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/codebase-design/SKILL.md · Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/diagnosing-bugs/SKILL.md · Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/domain-modeling/SKILL.md · Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/grill-with-docs/SKILL.md · A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/grilling/SKILL.md · Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/handoff/SKILL.md · Compact the current conversation into a handoff document for another agent to pick up.
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/i-have-adhd/SKILL.md · Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/impeccable/SKILL.md · Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/ponytail-audit/SKILL.md · Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/ponytail-review/SKILL.md · Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded…
dietrichgebert/ponytail · skills/ponytail-debt/SKILL.md · Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals…
dietrichgebert/ponytail · .openclaw/skills/ponytail-debt/SKILL.md · Harvest every ponytail: shortcut comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot…