ponytail-debt

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

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/marmelab/atomic-crm-demo-art-teaching --skill ponytail-debt-marmelab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ponytail-debt
Source: https://github.com/marmelab/atomic-crm-demo-art-teaching/tree/main/.claude/skills/ponytail-debt
Command: npx skills add https://github.com/marmelab/atomic-crm-demo-art-teaching --skill ponytail-debt-marmelab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deliberate code shortcuts marked with ponytail: comments are often forgotten over time, turning into permanent, untracked technical debt that slows down future development. This read-only Skill eliminates that risk by automatically collecting all such markers into a single, organized ledger without modifying any repository files.

Core Features & Use Cases

  • Read-Only Full Codebase Scan: Automatically searches all repository files for ponytail: comment markers, skipping irrelevant directories like node_modules, .git, and build output to avoid false positives, with no modifications to repository files.
  • Structured Ledger Output: Groups findings by file, and includes the simplified code context, named ceiling limit, and defined upgrade trigger for each shortcut.
  • Rot Risk Flagging: Highlights any ponytail: markers with no defined upgrade path, which are the most likely to be forgotten and become permanent debt.
  • Use Case: A development team can run this Skill at the end of a sprint to get a clear, actionable list of all deferred work, ensuring no shortcuts are left untracked.

Quick Start

Use the ponytail-debt skill to generate a complete ledger of all ponytail: code shortcuts in your current 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 from code shortcuts marked in comments?

You can track code shortcut technical debt by scanning your repository for ponytail: comment markers, which parses the ceiling limits and upgrade paths to generate a structured debt ledger without modifying any files.

What is a ponytail comment marker for deferred work?

A ponytail: comment marker is a deliberate code shortcut annotation used in software development to flag deferred work, specifying a named ceiling limit and a defined upgrade trigger for future resolution.

How do I generate a technical debt ledger for all deferred work in a repository?

To generate a technical debt ledger, scan all repository files while skipping node_modules and build output, grouping the ponytail: markers by file with their code context and flagging entries with no defined upgrade path.

Does the debt tracking scan modify my repository files?

No, the debt tracking scan is strictly read-only, meaning it harvests ponytail: comment markers and parses their metadata into a structured ledger without modifying or writing to any repository files.

How do I find deferred work markers that have no upgrade path?

Finding deferred work markers with no upgrade path involves scanning for ponytail: comments and flagging entries with no defined upgrade trigger, highlighting the rot risk of shortcuts likely to become permanent debt.

When should I scan my codebase for deliberate code shortcuts?

You should scan your codebase for deliberate code shortcuts at the end of a sprint to collect all ponytail: markers into an actionable debt ledger, ensuring no deferred work is left untracked.