Harvest ponytail comment markers into a tracked technical debt ledger.
npx skills add https://github.com/fusuyfusuy/dot-agents --skill ponytail-debt-fusuyfusuy
Please help me install this Agent Skill. Skill: ponytail-debt Source: https://github.com/fusuyfusuy/dot-agents/tree/main/skills/ponytail-debt Command: npx skills add https://github.com/fusuyfusuy/dot-agents --skill ponytail-debt-fusuyfusuy
ponytail: comments in code tend to be forgotten, turning intentional deferrals into untracked technical debt. This Skill scans the codebase for every ponytail marker and consolidates them into a verifiable debt ledger with explicit ceilings and upgrade triggers. ## Core Features & Use Cases - Marker Harvesting: Scans the repository for #, //, /* */, and -- style ponytail comments and parses their 3-tuple format (what, ceiling, upgrade trigger). - CI Validation Gate: Runs mimori debt check to verify marker schema validity and enforce a hard 30-line total debt ceiling, exiting non-zero on failure. - Ledger Synchronization: Syncs in-code markers into .agents/memory.md under ## KNOWN DEBT, preserving operator waivers and purging stale entries. - Use Case: Before a release, run the debt check to confirm all deferred shortcuts have concrete upgrade triggers and that total debt stays within the agreed ceiling. ## Quick Start Ask the agent to list all ponytail debt markers in the repository and sync them into the known debt ledger.High-intent search queries and answers about installing and using this skill.
Annotate deliberate shortcuts with ponytail comments in the format `ponytail: <what> <- <ceiling> -> <upgrade_trigger>`, then run the debt list command to harvest all markers across the repository into a single ledger.
Run `mimori debt check` in your CI pipeline. It validates that every marker has a concrete trigger and non-empty ceiling, asserts total debt stays under the 30-line ceiling, and exits with code 1 on any failure.
Yes, the Skill defines a fallback using grep with strict and loose passes that exclude .git, node_modules, and data or lock files. The fallback prints each marker with file, line, ceiling, and upgrade trigger.
A trigger is valid only when it specifies a concrete condition, dependency, size threshold, or event rather than a vague aspiration. Markers missing the ceiling or trigger separators are flagged as malformed during validation.
Use `mimori memory resolve` with a pattern matching the debt item. The memory lint step rejects completed checkboxes and strikethroughs, so resolved debt must be deleted rather than accumulated.
marmelabScan repository files for ponytail: comment markers and generate a structured debt ledger.
malinskibeniaminHarvest ponytail comments from codebase and generate a debt ledger.
FlexNetOSVerify code-analysis claims against actual source code.
endorphin-aiManage Jira issues via Atlassian MCP with creation, updates, linking, commenting, and JQL searches.