skills.rest
Jatinkrmahato993203
Jatinkrmahato993203COMMUNITY
Explore all skills by this author →
GitHub

ponytail-debt

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

Updated Jul 20, 2026
Search Tags:#refactoring#technical debt#code comments#grep#shortcuts#code scan#debt ledger
One-click install
npx skills add https://github.com/Jatinkrmahato993203/crime --skill ponytail-debt-jatinkrmahato993203
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ponytail-debt
Source: https://github.com/Jatinkrmahato993203/crime/tree/main/skills/ponytail-debt
Command: npx skills add https://github.com/Jatinkrmahato993203/crime --skill ponytail-debt-jatinkrmahato993203

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 entire codebase for those markers and compiles them into a single debt ledger so deferred work stays visible and trackable. ## Core Features & Use Cases - Codebase-wide scan: Greps for ponytail: comment markers across files while skipping node_modules, .git, and build output. - Structured ledger output: Produces one row per marker grouped by file, extracting the ceiling (limit) and upgrade path (trigger) from each comment. - Rot-risk flagging: Tags any marker missing an upgrade trigger as no-trigger so the riskiest deferrals stand out. - Use Case: After a fast-moving sprint where developers left ponytail: comments on temporary implementations, run the scan to get a complete ledger of what was deferred, why, and when to revisit it. ## Quick Start Ask the assistant to run ponytail debt and list every shortcut marked in this repository.

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

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. Each hit becomes a row grouped by file with the limit and revisit trigger extracted.

What format should a ponytail debt comment follow?▼

Use the convention `ponytail: <ceiling>, <upgrade path>` after a `#` or `//` comment prefix. The ceiling names the limit of the shortcut, and the upgrade path states the trigger for revisiting it.

Does the ponytail debt scan modify my code?▼

No, the scan is read-only and only reports findings. It changes nothing in the repository unless you explicitly ask it to persist the ledger to a file such as PONYTAIL-DEBT.md.

Which directories are excluded from the debt scan?▼

The grep scan skips `node_modules`, `.git`, and build output directories. This keeps generated and vendored code out of the ledger so only intentional source markers appear.

What happens to markers without an upgrade trigger?▼

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.

Related Skills

Explore More Software Engineering Skills→
engasnm111engasnm111
166

ponytail-debt

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

Community
Basic
miptah21miptah21
2

tech-debt-tracker

Scan codebases for technical debt and generate prioritized remediation plans.

Community
Intermediate
jorgealvesjorgealves
2

technical-debt-visualizer

Aggregate complexity, test coverage gaps, and change frequency to identify high-risk code hotspots.

Community
Advanced
AtharvaN16AtharvaN16

wayfinder

Create shared investigation ticket maps on issue trackers for project management.

Community
Advanced