Harvests ponytail: code comments into a grouped technical debt ledger report.
npx skills add https://github.com/epicodic/drift --skill ponytail-debt-epicodic
Please help me install this Agent Skill. Skill: ponytail-debt Source: https://github.com/epicodic/drift/tree/main/.agents/skills/ponytail-debt Command: npx skills add https://github.com/epicodic/drift --skill ponytail-debt-epicodic
ponytail: comments scatter across a codebase and quietly rot into permanent debt. This Skill collects every marker into one ledger so deferrals stay visible and tracked instead of being forgotten. ## Core Features & Use Cases - Codebase-wide scan: Greps for ponytail: comment markers across the repo, 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: Before a sprint planning session, run the scan to list every deferred shortcut with its revisit trigger, then optionally persist the report to PONYTAIL-DEBT.md. ## Quick Start Ask the assistant 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:` 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.
The convention is `ponytail: <ceiling>, <upgrade path>` placed as a code comment. The ceiling names what was simplified, and the upgrade path names the trigger that should prompt revisiting the shortcut.
No, the scan is strictly read-only and changes nothing in the repository. It only greps for markers and prints a report; persisting the ledger to a file like PONYTAIL-DEBT.md happens only if you explicitly ask.
The grep scan skips `node_modules`, `.git`, and build output directories. It searches for `#` and `//` comment prefixes, and other comment prefixes can be added for stacks that use them.
Any `ponytail:` comment that names no upgrade path or trigger gets a `no-trigger` tag in the ledger. These are flagged as the highest rot risk because they can silently become permanent.
marmelabScan repository files for ponytail: comment markers and generate a structured debt ledger.
openyakPlan and document a sprint with goals, capacity, and backlog.
Devsoul2026Automate pre-commit verification with static analysis, tests, and lint checks.
wanghaishengScan codebases for technical debt indicators and generate prioritized debt reports.