Harvests ponytail: code comments into a grouped technical debt ledger report.
npx skills add https://github.com/timikalo7/Execute --skill ponytail-debt-timikalo7
Please help me install this Agent Skill. Skill: ponytail-debt Source: https://github.com/timikalo7/Execute/tree/main/.claude/skills/ponytail-debt Command: npx skills add https://github.com/timikalo7/Execute --skill ponytail-debt-timikalo7
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 and trackable instead of being forgotten. ## Core Features & Use Cases - Repo-wide marker scan: Greps for ponytail: comment markers while skipping node_modules, .git, and build output. - Structured ledger output: Groups one row per marker by file, extracting the ceiling (what was simplified) and the upgrade trigger from each comment. - Rot-risk flagging: Tags any marker missing an upgrade path as no-trigger, highlighting the deferrals most likely to silently become permanent. - Use Case: After a fast build sprint, run the ledger to list every shortcut the team deferred, see which ones lack a revisit trigger, and optionally persist the report to PONYTAIL-DEBT.md. ## Quick Start Ask the agent to run ponytail-debt and list every shortcut marked in the codebase with its ceiling and upgrade trigger.High-intent search queries and answers about installing and using this skill.
Mark each deliberate shortcut with a `ponytail: <ceiling>, <upgrade path>` comment, then run this Skill to grep the repo and compile every marker into a grouped ledger showing file, line, what was simplified, and the revisit trigger.
Use the convention `ponytail: <ceiling>, <upgrade path>` after a `#` or `//` comment prefix. The ceiling names what was simplified and the upgrade path names the trigger to revisit it; markers without a trigger get flagged as no-trigger.
No, the scan is strictly read-only and only reports findings. If you want the ledger persisted, you must explicitly ask, and it will write the output to a file such as PONYTAIL-DEBT.md.
The grep-based scan skips `node_modules`, `.git`, and build output directories. You can extend the comment prefix pattern beyond `#` and `//` if your stack uses other comment syntaxes.
Any `ponytail:` comment that names no upgrade path or trigger is automatically tagged `no-trigger` in the ledger. The summary line reports the total marker count and how many lack triggers, highlighting the entries most at risk of rotting.
marmelabScan repository files for ponytail: comment markers and generate a structured debt ledger.
ronniepinnellReview backlog items and prioritize work for upcoming sprints.
jorgealvesAggregate complexity, test coverage gaps, and change frequency to identify high-risk code hotspots.
stakworkTrack open regulatory comment periods and log filing decisions.