ponytail-debt

Harvests ponytail: code comments into a grouped technical debt ledger report.

Updated May 26, 2026
One-click install
npx skills add https://github.com/avel123111/triplanio --skill ponytail-debt-avel123111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ponytail-debt
Source: https://github.com/avel123111/triplanio/tree/main/.claude/skills/ponytail-debt
Command: npx skills add https://github.com/avel123111/triplanio --skill ponytail-debt-avel123111

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deliberate shortcuts marked with ponytail: comments scatter across a codebase and quietly rot into permanent debt. This Skill collects every marker into one ledger so deferred work stays visible instead of becoming "later means never". ## Core Features & Use Cases - Repo-wide scan: Greps for ponytail: comment markers (skipping node_modules, .git, and build output) and turns each hit into a ledger row with file, line, ceiling, and upgrade trigger. - Rot-risk flagging: Any marker missing an upgrade path gets a no-trigger tag, highlighting the deferrals most likely to silently become permanent. - Optional ownership: Add git blame per line to attach an owner to each debt row. - Use Case: Before a sprint planning session, run the scan to list every shortcut the team deliberately took, grouped by file, so you can decide which deferred items to schedule. ## Quick Start Ask the assistant to run ponytail debt and list every shortcut marked in this repository.

Frequently Asked Questions about ponytail-debt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track technical debt comments in my codebase?

Mark each deliberate shortcut with a `ponytail:` comment naming its ceiling and upgrade path, then run the scan to grep all markers into one ledger grouped by file. Each row shows the file, line, what was simplified, and the trigger to revisit it.

How to find deferred shortcuts before they become permanent?

Run the ponytail debt scan, which greps the repo for `ponytail:` comment markers while skipping node_modules, .git, and build output. Markers without an upgrade path get a `no-trigger` tag so the riskiest deferrals stand out.

Does the ponytail debt scan modify my code?

No, the scan is read-only and changes nothing in the repository. It only reports the ledger, and it writes the output to a file like PONYTAIL-DEBT.md only if you explicitly ask it to persist the results.

Can I see who wrote each debt marker?

Yes, add `git blame -L<line>,<line>` per marker to attach an owner to each ledger row. This is optional and layered on top of the basic file-and-line report.

What comment formats does the debt scan support?

The default grep pattern matches `#` and `//` comment prefixes before `ponytail:`. If your stack uses other comment syntaxes, extend the grep pattern with additional prefixes so those markers are captured too.