skills.rest
cloudofgeorge
cloudofgeorgeCOMMUNITY
Explore all skills by this author →
Website𝕏@cloudofgeorgeGitHub

ponytail-debt

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

Updated May 11, 2026
Search Tags:#refactoring#technical debt#code comments#code audit#grep#git blame#debt ledger
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill ponytail-debt-cloudofgeorge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ponytail-debt
Source: https://github.com/cloudofgeorge/AI-hands-Engineer/tree/main/skills/engineering/optimization/ponytail/ponytail-debt
Command: npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill ponytail-debt-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deliberate shortcuts marked with ponytail: comments scatter across a codebase and quietly rot into permanent debt. This Skill greps every marker into a single ledger so deferred work stays visible and each shortcut keeps its named ceiling and upgrade trigger. ## Core Features & Use Cases - Marker Harvesting: 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 and upgrade path from each comment, with optional git blame ownership. - Rot Detection: Flags any marker missing an upgrade trigger with a no-trigger tag so silent debt stands out. - Use Case: After a fast implementation sprint, run the ledger to list every deferred shortcut, see which ones lack a revisit trigger, and decide what to schedule next. ## Quick Start Ask the agent to run ponytail-debt and list every ponytail marker in the repository as a debt ledger.

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?▼

Grep the repository for a consistent comment marker such as `ponytail:` and compile each hit into a ledger row with file and line number. Grouping rows by file and extracting the ceiling and upgrade path from each comment keeps deferred work visible.

How do I find all ponytail markers in my repo?▼

Run `grep -rnE '(#|//) ?ponytail:' .` from the repo root, excluding node_modules, .git, and build output. Each match becomes one ledger row, and you can add other comment prefixes for your stack.

Can I see who wrote each debt marker?▼

Yes, run `git blame -L<line>,<line>` on each marker's line to attribute ownership per row. This is optional and added on top of the base ledger output.

What happens to markers without an upgrade path?▼

Any ponytail comment that names no upgrade path or trigger gets a `no-trigger` tag in the ledger. These are flagged as rot risks because they can silently become permanent.

Does the debt ledger modify my code?▼

No, it only reads and reports, changing nothing in the codebase. If you want to persist the result, it writes the ledger to a file such as PONYTAIL-DEBT.md only when asked.

Related Skills

Explore More Software Engineering Skills→
dsonyydsonyy

ponytail-debt

Collects ponytail: code comments into a technical debt ledger report.

Community
Basic
ronniepinnellronniepinnell

sprint

Review backlog items and prioritize work for upcoming sprints.

Community
Intermediate
XinAlohaXinAloha
3

ponytail-debt

Scan source files for ponytail comments and generate a debt ledger.

Community
Basic
matthew-johnsonmatthew-johnson

github-issues

Create, triage, label, and assign GitHub issues via gh CLI or REST API.

Community
Advanced