skills.rest
Reimonsk8
Reimonsk8COMMUNITY
Explore all skills by this author →
Website𝕏@reimonsk8GitHub

ponytail-debt

Collects ponytail shortcut comments from a repository into one technical debt ledger.

Updated May 29, 2026
Search Tags:#refactoring#technical debt#code comments#grep#git blame#code scan#debt ledger
One-click install
npx skills add https://github.com/Reimonsk8/hermes-9router-model-balancing --skill ponytail-debt-reimonsk8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ponytail-debt
Source: https://github.com/Reimonsk8/hermes-9router-model-balancing/tree/main/plugins/ponytail/.openclaw/skills/ponytail-debt
Command: npx skills add https://github.com/Reimonsk8/hermes-9router-model-balancing --skill ponytail-debt-reimonsk8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deliberate shortcuts marked with ponytail: comments scatter across a codebase and quietly become permanent. This Skill scans the repository and consolidates every marker into a single debt ledger so deferred work stays visible and tracked. ## Core Features & Use Cases - Repository-wide scan: Greps for ponytail: comment markers 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 trigger from each comment, with optional git blame ownership. - Rot-risk flagging: Tags markers that name no upgrade path as no-trigger, highlighting the deferrals most likely to silently rot. - Use Case: Before a sprint planning session, run the scan to get a report like src/auth.py:42 — simplified token refresh. ceiling: single provider. upgrade: add OAuth2 support. ending with a summary count of markers and no-trigger entries. ## Quick Start Ask the assistant to scan this repository for ponytail debt markers and produce the ledger report.

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

Mark each deliberate shortcut with a `ponytail: <ceiling>, <upgrade path>` comment, then run this scan to grep all markers into one ledger. Each row shows the file, line, what was simplified, its limit, and the trigger to revisit it.

What comment format does the ponytail debt scan recognize?▼

It matches lines containing `# ponytail:` or `// ponytail:` via the regex `(#|//) ?ponytail:`. The comment should follow the convention `ponytail: <ceiling>, <upgrade path>` so the ceiling and trigger can be extracted directly.

Does the scan work with languages other than hash and slash comments?▼

The default grep pattern covers `#` and `//` comment prefixes. If your stack uses other comment syntaxes, extend the grep pattern with additional prefixes as noted in the instructions.

Can I see who wrote each ponytail debt marker?▼

Yes, add `git blame -L<line>,<line>` for each marker line to attach an owner per row. This is optional and layered on top of the base ledger output.

Does the ponytail debt scan modify my repository files?▼

No, it reads and reports only. The ledger is printed as a one-shot report, and it is written to a file such as PONYTAIL-DEBT.md only if you explicitly ask.

Related Skills

Explore More Software Engineering Skills→
azishioazishio

anti-overengineering-debt

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

Community
Basic
miptah21miptah21
2

tech-debt-tracker

Scan codebases for technical debt and generate prioritized remediation plans.

Community
Intermediate
ImaginerLabsImaginerLabs

quality-analyst

Assess code quality and quantify technical debt across a codebase.

Official
Intermediate
nextflow-ionextflow-io
261

Find TODO and FIXME Comments

Detect and categorize TODO and FIXME comments in Markdown, Nextflow, and config files.

Official
Basic