ponytail-debt

oleh dietrichgebert

Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail ledger", or "what did we mark to do later". One-shot report, changes nothing.

npx skills add https://github.com/dietrichgebert/ponytail --skill ponytail-debt

Unduh ZIP GitHub

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 named>. upgrade: <the trigger to revisit>.

The convention is ponytail: <ceiling>, <upgrade path>, so pull the ceiling and the trigger straight from the comment. Want an owner per row too? add git blame -L<line>,<line>.

Flag the rot risk: any ponytail: comment that names no upgrade path or trigger gets a no-trigger tag, those are the ones that silently rot.

End with <N> markers, <M> with no trigger. Nothing found: No ponytail: debt. Clean ledger.

Boundaries

Reads and reports only, changes nothing. To persist it, ask and it writes the ledger to a file (e.g. PONYTAIL-DEBT.md). One-shot. "stop ponytail-debt" or "normal mode" to revert.

Lebih banyak skill dari dietrichgebert

Memaksa solusi paling malas yang benar-benar berfungsi, paling sederhana, terpendek, paling minimal. Menyalurkan senior dev yang sudah melihat semuanya: pertanyakan apakah tugas itu perlu ada sama sekali (YAGNI), gunakan pustaka standar sebelum kode kustom, fitur platform asli sebelum dependensi, satu baris sebelum lima puluh. Mendukung tingkat intensitas: lite, full (default), ultra. Gunakan kapan pun pengguna mengatakan "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", atau...

developmentcode-review

ponytail-review

Tinjauan kode yang hanya berfokus pada over-engineering. Menemukan apa yang harus dihapus: pustaka standar yang diciptakan ulang, dependensi yang tidak diperlukan, abstraksi spekulatif, fleksibilitas mati. Satu baris per temuan: lokasi, apa yang dipotong, apa penggantinya. Gunakan saat pengguna mengatakan "tinjau untuk over-engineering", "apa yang bisa kita hapus", "apakah ini over-engineered", "tinjauan sederhana", atau memanggil /ponytail-review. Melengkapi tinjauan yang berfokus pada kebenaran, yang ini hanya memburu kompleksitas.

code-reviewdevelopment

Audit seluruh repositori untuk over-engineering. Seperti ponytail-review, tetapi memindai seluruh basis kode, bukan hanya diff: daftar peringkat tentang apa yang harus dihapus, disederhanakan, atau diganti dengan padanan stdlib/native. Gunakan saat pengguna mengatakan "audit basis kode ini", "audit untuk over-engineering", "apa yang bisa saya hapus dari repositori ini", "cari bloat", "ponytail-audit", atau "/ponytail-audit". Laporan sekali jalan, tidak menerapkan perbaikan.

code-reviewdevelopment

Kartu referensi cepat untuk semua mode, skill, dan perintah ponytail. Tampilan sekali pakai, bukan mode persisten. Pemicu: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".