skills.rest
Sambhav242005
Sambhav242005COMMUNITY
Explore all skills by this author →
WebsiteGitHub

ponytail-debt

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

Updated Aug 7, 2026
Search Tags:#refactoring#technical debt#code comments#grep#shortcuts#code scan#debt ledger
One-click install
npx skills add https://github.com/Sambhav242005/Major-Project --skill ponytail-debt-sambhav242005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ponytail-debt
Source: https://github.com/Sambhav242005/Major-Project/tree/main/.agents/skills/ponytail-debt
Command: npx skills add https://github.com/Sambhav242005/Major-Project --skill ponytail-debt-sambhav242005

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 repository for those markers and compiles them into a single debt ledger so deferred work stays visible and trackable. ## Core Features & Use Cases - Repository-wide scan: Greps for ponytail: comment markers across the codebase while skipping node_modules, .git, and build output. - Structured ledger output: Produces one row per marker grouped by file, extracting the ceiling (the limit) and the upgrade path (the trigger to revisit) from each comment. - Rot-risk flagging: Tags any marker missing an upgrade trigger as no-trigger, highlighting the deferrals most likely to rot. - Use Case: Before a sprint planning session, run the scan to list every shortcut the team deliberately deferred, then decide which ones to schedule based on their named ceilings and triggers. ## 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 this scan to grep all markers into one ledger. Each row shows the file, line, what was simplified, and the trigger to revisit it.

How to find deferred shortcuts before they become permanent?▼

Run the ponytail debt scan, which greps the repo for `ponytail:` comment markers and compiles them into a grouped ledger. Markers without an upgrade trigger get a `no-trigger` tag so the riskiest deferrals stand out.

Does the ponytail debt scan modify my code?▼

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

What comment formats does the debt scan support?▼

The default grep pattern matches `#` and `//` comment prefixes followed by `ponytail:`. If your stack uses other comment syntaxes, you can extend the pattern with additional prefixes so those markers are captured too.

Why are some ledger rows tagged no-trigger?▼

A row gets the `no-trigger` tag when its `ponytail:` comment names no upgrade path or revisit trigger. These entries are flagged because deferrals without a defined trigger are the ones most likely to silently become permanent.

Related Skills

Explore More Software Engineering Skills→
marmelabmarmelab

ponytail-debt

Scan repository files for ponytail: comment markers and generate a structured debt ledger.

Official
Intermediate
azishioazishio

anti-overengineering-debt

Collects anti-overengineering comment markers into a grouped technical debt ledger report.

Community
Basic
ImaginerLabsImaginerLabs

quality-analyst

Assess code quality and quantify technical debt across a codebase.

Official
Intermediate
teocraftersteocrafters

e2e-testing

Orchestrate E2E testing workflows from feature analysis to Playwright test implementation and healing.

Official
Advanced