ponytail-debt

Collects ponytail comment markers from a codebase into a technical debt ledger.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/Rasslonely/NexusXRP --skill ponytail-debt-rasslonely
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ponytail-debt
Source: https://github.com/Rasslonely/NexusXRP/tree/main/.agents/skills/ponytail-debt
Command: npx skills add https://github.com/Rasslonely/NexusXRP --skill ponytail-debt-rasslonely

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deliberate shortcuts marked with ponytail: comments scatter across a codebase and quietly rot into permanent workarounds. This Skill harvests every marker into a single ledger so deferred work stays visible and each deferral keeps its named ceiling and upgrade trigger. ## Core Features & Use Cases - Marker Scanning: Greps the repository for ponytail: comment markers while skipping node_modules, .git, and build output. - Structured Ledger: Groups one row per marker by file with the simplification, its ceiling, and its upgrade trigger, with optional git blame ownership per row. - Rot Detection: Flags any marker missing an upgrade path with a no-trigger tag so silent deferrals surface immediately. - Use Case: Before a sprint review, ask for the ponytail ledger to see every shortcut the team deliberately took, which ones have no revisit trigger, and who owns each line. ## Quick Start Ask the assistant to run ponytail debt and list every shortcut marked in the repository with its ceiling and upgrade trigger.

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 a codebase?

Track technical debt by grepping the repository for a consistent comment marker such as `ponytail:` and compiling each hit into a ledger row. This Skill scans with grep, skipping node_modules, .git, and build output, and groups results by file with line numbers.

How to find deferred shortcuts left in source code?

Run the ponytail debt scan, which searches for `(#|//) ?ponytail:` comment patterns across the repo. Each marker names what was simplified, its ceiling, and the trigger to revisit, so deferred work is listed instead of forgotten.

Does the ponytail debt scan modify my code?

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

What happens if a debt marker has no upgrade path?

Any `ponytail:` comment that names no upgrade path or trigger gets a `no-trigger` tag in the ledger. These flagged rows are the ones most likely to silently rot into permanent workarounds.

Can I see who wrote each debt marker?

Yes, the ledger supports optional ownership per row by running `git blame -L<line>,<line>` on each marker's line. This attributes every shortcut to the commit author who introduced it.