skills.rest
engasnm111
engasnm111COMMUNITY
Explore all skills by this author →
GitHub

ponytail-debt

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

166|78|Updated Aug 10, 2026
Search Tags:#refactoring#technical debt#code comments#grep#shortcuts#code scanning#debt ledger
One-click install
npx skills add https://github.com/engasnm111/lnwjud --skill ponytail-debt-engasnm111
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ponytail-debt
Source: https://github.com/engasnm111/lnwjud/tree/main/.agents/skills/ponytail-debt
Command: npx skills add https://github.com/engasnm111/lnwjud --skill ponytail-debt-engasnm111

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deliberate shortcuts marked with ponytail: comments tend to be forgotten and silently become permanent. This Skill scans the repository for every such marker and compiles them into a single debt ledger so deferred work stays visible and trackable. ## 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 (limit) and upgrade path (trigger) from each comment. - Rot Detection: Flags markers that name no upgrade trigger with a no-trigger tag, highlighting the debt most likely to be forgotten. - 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 ponytail marker in this repository with its ceiling and upgrade trigger.

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 markers in my codebase?▼

Run a grep scan for structured comment markers like `ponytail:` across the repository, excluding node_modules, .git, and build output. Each hit becomes a ledger row showing the file, line, the limitation named, and the trigger to revisit it.

What is the ponytail comment convention for deferred work?▼

The convention is `ponytail: <ceiling>, <upgrade path>` written as a code comment. The ceiling names the current limitation and the upgrade path names the trigger that should prompt revisiting the shortcut.

Does the ponytail-debt scan modify any files?▼

No, the scan is read-only and only reports findings. If you want the ledger persisted, you must explicitly ask, and it will write the report to a file such as PONYTAIL-DEBT.md.

How do I find deferred shortcuts that have no revisit plan?▼

Markers that name no upgrade path or trigger are flagged with a `no-trigger` tag in the ledger. These rows represent the highest rot risk because nothing prompts the team to revisit them.

Can I see who wrote each ponytail debt marker?▼

Yes, the ledger supports optional ownership attribution by running `git blame -L<line>,<line>` for each marker line, adding the responsible author to each row.

Related Skills

Explore More Software Engineering Skills→
RazisafirRazisafir
1

ponytail-debt

Lists deliberate code shortcuts and deferrals marked with 'ponytail:' comments using grep.

Community
Intermediate
intraleintrale

planner

Automate strategic project planning, sprint scheduling, and task prioritization for software teams.

Official
Advanced
sburlsburl
26

techdebt

Detect and remediate technical debt in JavaScript, TypeScript, Python, and Rust codebases.

Community
Advanced
XinAlohaXinAloha
3

ponytail-debt

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

Community
Basic