Collects ponytail: code comments into a technical debt ledger report.
npx skills add https://github.com/CYRUS-pinto/pi-bot --skill ponytail-debt-cyrus-pinto
Please help me install this Agent Skill. Skill: ponytail-debt Source: https://github.com/CYRUS-pinto/pi-bot/tree/main/.agents/skills/ponytail-debt Command: npx skills add https://github.com/CYRUS-pinto/pi-bot --skill ponytail-debt-cyrus-pinto
ponytail: comments scatter across a codebase and quietly rot into permanent debt. This Skill greps the repository for every marker and compiles them into a single ledger so deferred work stays visible instead of being forgotten. ## Core Features & Use Cases - Marker Scanning: Greps the repo for ponytail: comment markers while skipping node_modules, .git, and build output. - Structured Ledger: Outputs one row per marker grouped by file, extracting the ceiling (the limit) and the upgrade trigger from each comment. - Rot Detection: Flags any marker missing an upgrade path with a no-trigger tag so the riskiest deferrals stand out. - Use Case: Before a sprint planning session, run the scan to list every shortcut ponytail left behind, see which ones have no revisit trigger, and decide what to pay down. ## Quick Start Ask the assistant to run ponytail-debt and list every ponytail marker in this repository with its ceiling and upgrade trigger.High-intent search queries and answers about installing and using this skill.
Grep the repository for a consistent comment marker such as `ponytail:` and compile each hit into a ledger row with file, line, and the deferral reason. This Skill automates that scan and groups results by file with ceiling and upgrade-trigger fields.
Say "ponytail debt" or "/ponytail-debt" and the Skill greps the repo for `ponytail:` comments, skipping node_modules, .git, and build output. It prints one ledger row per marker and a summary count.
No, the scan is strictly 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.
A no-trigger tag marks any `ponytail:` comment that names no upgrade path or revisit condition. These entries are flagged because without a trigger they silently rot into permanent debt.
Yes, the Skill supports adding ownership per row by running `git blame -L<line>,<line>` on each marker line. This attributes every ledger entry to the commit author who left the shortcut.
marmelabScan repository files for ponytail: comment markers and generate a structured debt ledger.
Andy-HNUPrioritize technical debt and generate incremental refactoring plans.
ImaginerLabsAssess code quality and quantify technical debt across a codebase.
MWest2020Harvest ponytail comment markers from a codebase into a technical debt ledger.