skills.rest
Chensihakniroth
ChensihaknirothCOMMUNITY
Explore all skills by this author →
GitHub

ponytail-debt

Scans repositories for ponytail comment markers and compiles them into a technical debt ledger.

Updated Jun 7, 2026
Search Tags:#refactoring#technical debt#code comments#grep#repository maintenance#code scanning#debt ledger
One-click install
npx skills add https://github.com/Chensihakniroth/ANAKOT-AGENT --skill ponytail-debt-chensihakniroth
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ponytail-debt
Source: https://github.com/Chensihakniroth/ANAKOT-AGENT/tree/main/skills/ponytail/.openclaw/skills/ponytail-debt
Command: npx skills add https://github.com/Chensihakniroth/ANAKOT-AGENT --skill ponytail-debt-chensihakniroth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deliberate shortcuts marked with ponytail: comments often get forgotten and silently become permanent. This Skill collects every marker into one ledger so deferred work stays visible and tracked. ## Core Features & Use Cases - Marker Scanning: Greps the repository for ponytail: comment markers while skipping node_modules, .git, and build output. - Debt Ledger Report: Groups one row per marker by file, extracting the ceiling (limit) and upgrade path (revisit trigger) from each comment. - Rot-Risk Flagging: Tags markers with no named upgrade trigger as no-trigger, highlighting the deferrals most likely to silently rot. - Use Case: Before a sprint planning session, run the scan to produce a ledger of all deferred shortcuts, then optionally persist it to PONYTAIL-DEBT.md for the team to triage. ## Quick Start Ask the agent to scan this repository for ponytail markers and report the debt ledger grouped by file.

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

Mark each deliberate shortcut with a `ponytail:` comment naming its ceiling and upgrade path, then grep the repo for those markers. The scan compiles every hit into a ledger grouped by file with the limit and revisit trigger extracted.

What is the ponytail comment convention for deferrals?▼

The convention is `ponytail: <ceiling>, <upgrade path>` placed as a code comment. The ceiling names the current limit of the simplification, and the upgrade path names the trigger that should prompt revisiting it.

Does the ponytail-debt scan modify my source files?▼

No, the scan reads and reports only and changes nothing in the repository. Persisting the ledger to a file such as PONYTAIL-DEBT.md happens only when explicitly requested.

Which files are excluded from the ponytail marker scan?▼

The grep scan skips node_modules, .git, and build output directories. You can add other comment prefixes beyond # and // if your stack uses different syntax.

What happens when a ponytail comment has no upgrade path?▼

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

Related Skills

Explore More Software Engineering Skills→
Base-AnaliticaBase-Analitica

ponytail-debt

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

Official
Basic
LordKuperLordKuper

bug-triage

Triage open bugs into prioritized, sprint-aligned action items.

Community
Advanced
DayzideeDayzidee

ponytail-debt

Collect ponytail shortcuts from code comments into a debt ledger.

Community
Basic
specvitalspecvital
1

comment-review

Analyze source code to remove unnecessary comments and enforce TODO ownership.

Official
Advanced