ponytail-debt
The ponytail-debt skill scans a codebase for comments prefixed with ponytail: to generate a report of technical debt. It extracts the ceiling and upgrade path from each comment to track deferred tasks.
Is ponytail-debt safe to install?
Review the source first: our audit of ponytail-debt's source files found 2 shell commands, 0 external URLs, file reads and writes (high risk). Every command and URL listed appears verbatim in the skill's source. The skill executes shell commands to scan the repository and can write a ledger file to the local filesystem upon user request.
How we audit skills: our security review methodology.
Who is this skill for?
Developers and project managers who need to track deliberate shortcuts and deferred tasks marked in the codebase.
What can you do with it?
- Identify technical debt marked with ponytail: comments.
- Generate a ledger of shortcuts and their associated upgrade triggers.
- Detect stale debt markers that lack an upgrade path.
How good is this skill?
Quality score: 5/10. The skill documentation is clear and provides specific instructions for implementation and usage. The scope is well-defined.
What does the skill file contain?
Every deliberate ponytail shortcut is marked with a `ponytail:` comment naming its ceiling and upgrade path. This collects them into one ledger so a deferral can't quietly become permanent. ## Scan Grep the repo for comment markers, skipping `node_modules`, `.git`, and build output: `grep -rnE '(#|//) ?ponytail:' .` (add other comment prefixes if your stack uses them) Each hit is one ledger row. The comment prefix keeps prose that merely mentions the convention out of the ledger. ## Output One row per marker, grouped by file: `<file>:<line>, <what was simplified>. ceiling: <the limit n...
Frequently asked questions
Does this skill modify the codebase?
No. It performs a read-only scan by default. It only writes a ledger file if the user explicitly requests it.
How does the skill identify debt?
It searches for comments containing the string ponytail: using a grep command, excluding node_modules, .git, and build output.
What happens if a comment lacks an upgrade path?
The skill tags the entry as no-trigger to indicate a risk of silent rot.
Related skills
github-actions-docs
264.6KDevelopers and DevOps engineers working with GitHub Actions workflows
The github-actions-docs skill provides grounded answers to GitHub Actions queries by retrieving information from official GitHub documentation. It assists with workflow syntax, security, migration, and runner configuration.
brainstorming
256.4KDevelopers and project managers who need to define requirements, architecture, and design for software projects before writing code
A structured brainstorming framework that guides users through project exploration, design proposal, and specification before implementation. It enforces a strict design-first workflow, requiring user approval for designs and documentation before transitioning to the writing-plans skill.
caveman-help
225.2KUsers who want to quickly reference caveman mode triggers, skill commands, and configuration options
The caveman-help skill provides a reference card for caveman modes, skills, and commands. It displays information in a compressed, caveman-style format upon user request.
writing-plans
174.7KSoftware engineers and AI agents tasked with implementing complex features from specifications
The writing-plans skill generates structured, task-based implementation plans for software development projects. It enforces a specific markdown format that includes architecture, tech stack, global constraints, and granular, test-driven development steps for each task.