Harvest ponytail comment markers from a codebase into a technical debt ledger.
npx skills add https://github.com/MWest2020/skill-forge --skill ponytail-debt-mwest2020
Please help me install this Agent Skill. Skill: ponytail-debt Source: https://github.com/MWest2020/skill-forge/tree/main/skills/ponytail-debt Command: npx skills add https://github.com/MWest2020/skill-forge --skill ponytail-debt-mwest2020
ponytail: comments tend to rot into permanent deferrals because nobody tracks them. This Skill scans the codebase for every such marker and compiles them into a single ledger so deferred work stays visible instead of becoming "later means never". ## Core Features & Use Cases - Marker Scanning: Greps the repository for ponytail: comment markers across comment styles (#, //), skipping node_modules, .git, and build output. - Structured Ledger: Outputs one row per marker grouped by file, extracting the ceiling (the limit named) and the upgrade trigger from each comment, with optional git blame ownership per row. - Rot Detection: Flags any marker lacking an upgrade path with a no-trigger tag, surfacing the deferrals most likely to silently become permanent. - Use Case: After a fast-moving sprint where the team deliberately cut corners, run the scan to produce a debt ledger like src/api.py:42 — in-memory cache. ceiling: single instance. upgrade: move to Redis when scaling horizontally. ## Quick Start Ask the agent 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.
Mark each deliberate shortcut with a `ponytail:` comment naming its ceiling and upgrade path, then run this scan to grep all markers into one ledger. Each row shows the file, line, what was simplified, and the trigger to revisit it.
It matches `# ponytail:` and `// ponytail:` comment prefixes via grep, and other prefixes can be added for your stack. The convention is `ponytail: <ceiling>, <upgrade path>`, so both fields are pulled directly from the comment text.
No, it is strictly read-only and produces a one-shot report. If you want the ledger persisted, you must explicitly ask, and it will write it to a file such as PONYTAIL-DEBT.md.
Any `ponytail:` comment that names no upgrade path or trigger is automatically tagged `no-trigger` in the ledger. These flagged rows are the deferrals most at risk of silently rotting into permanent shortcuts.
Yes, ownership is optional. Adding `git blame -L<line>,<line>` per row attributes each marker to its author, which helps route follow-up work to the right person.
Base-AnaliticaHarvests ponytail comment markers from a codebase into a technical debt ledger.
ronniepinnellReview backlog items and prioritize work for upcoming sprints.
app-vitalsScan codebases for principle violations and generate structured entropy reports.
growmaxInstalls the gsecure test-build layer into a project non-destructively and gathers project context.