skills.rest
hhenrichsen
hhenrichsenCOMMUNITY
Explore all skills by this author →
Website𝕏@hhenrichsen_GitHub

ponytail--ponytail-debt

Harvests ponytail: code comments into a grouped technical debt ledger report.

Updated Dec 3, 2025
Search Tags:#technical debt#code comments#reporting#code audit#grep#shortcuts#debt ledger
One-click install
npx skills add https://github.com/hhenrichsen/dots --skill ponytail-ponytail-debt-hhenrichsen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ponytail--ponytail-debt
Source: https://github.com/hhenrichsen/dots/tree/main/dot_skills/ponytail/ponytail-debt
Command: npx skills add https://github.com/hhenrichsen/dots --skill ponytail-ponytail-debt-hhenrichsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deliberate shortcuts marked with ponytail: comments scatter across a codebase and quietly rot into permanent deferrals. This Skill collects every marker into one ledger so deferred work stays visible and trackable instead of being forgotten. ## Core Features & Use Cases - Repo-wide marker scan: Greps for ponytail: comment markers while skipping node_modules, .git, and build output. - Structured ledger output: Groups one row per marker by file, extracting the ceiling (limit) and upgrade path (revisit trigger) from each comment. - Rot-risk flagging: Tags any marker lacking an upgrade trigger as no-trigger so the riskiest deferrals stand out. - Use Case: Before a sprint planning session, run the scan to list every shortcut ponytail left behind, see which ones name no revisit trigger, and decide what to pay down. ## Quick Start Ask the AI to run ponytail debt and list every shortcut marked in this repository.

Frequently Asked Questions about ponytail--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?▼

Run a grep scan for `ponytail:` comment markers across the repo, excluding node_modules, .git, and build output. Each hit becomes a ledger row grouped by file, showing the shortcut's ceiling and upgrade trigger.

How to find deferred shortcuts left in code?▼

Search for comment markers following the `ponytail: <ceiling>, <upgrade path>` convention. The scan reports each marker with its file and line, and flags any marker that names no revisit trigger as a rot risk.

Does the debt scan modify my source files?▼

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

What comment formats does the marker scan support?▼

The default pattern matches `#` and `//` comment prefixes via `grep -rnE '(#|//) ?ponytail:'`. You can add other comment prefixes if your stack uses different syntax, keeping prose mentions out of the ledger.

Why are some debt markers flagged as no-trigger?▼

A marker gets the `no-trigger` tag when its comment names no upgrade path or revisit condition. These are the deferrals most likely to silently become permanent, so the summary counts them separately.

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
NUMU-IONUMU-IO
2

speckit-security-review-followup

Convert security review findings into backlog-ready remediation and technical debt plans.

Official
Intermediate
xrcodexcodexrcodexcode
3

code-auditor

Performs static analysis and security audits on codebase files with structured remediation reports.

Community
Basic
EpicenterHQEpicenterHQ
4.8k

wayfinder

Plans multi-session work as decision tickets tracked on a repository issue tracker.

Official
Advanced