List every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Every deliberate ponytail shortcut is marked with a shortcut: comment naming
its ceiling and upgrade path (older code may say ponytail:). This collects them into one ledger so a deferral
can't quietly become permanent.
Grep the repo for comment markers, skipping node_modules, .git, and build
output:
grep -rnE --exclude-dir=.git --exclude-dir=node_modules --exclude-dir=dist --exclude-dir=build '(#|//|/[*]) ?(shortcut|ponytail):' . (add other comment prefixes if your stack uses them)
If the user names their own marker word (/ponytail-debt TODO), grep for that word instead.
Each hit is one ledger row. The comment prefix keeps prose that merely mentions the convention out of the ledger. Skip hits that are not a deferral, like a note about a keyboard shortcut.
One row per marker, grouped by file:
<file>:<line>, <what was simplified>. ceiling: <the limit named>. upgrade: <the trigger to revisit>.
The convention is shortcut: <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 marker 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 shortcut debt. Clean ledger.
Reads and reports only; never writes, edits, stages, or persists a ledger. One-shot. "stop ponytail-debt" or "normal mode" to revert.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Read public X/Twitter post URLs as structured evidence through the ADHX API. Use for relevant user-provided or research-discovered x.com, twitter.com, or adhx.com links. ADHX does not search X, and long-form Article content may be incomplete.
日本語の概要は準備中です。原文の説明を表示しています。
Shared vocabulary for designing deep modules, interfaces, seams, adapters, leverage, and locality. Use when designing or reshaping module boundaries, making code more testable, or evaluating interface depth.
日本語の概要は準備中です。原文の説明を表示しています。
Disciplined diagnosis loop for hard bugs, regressions, flaky failures, and performance problems with unclear cause. Use for root-cause debugging after a concrete symptom exists; do not use for routine implementation or speculative cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Route requests for current library, framework, SDK, API, CLI, or cloud-service documentation through available documentation tools and primary sources.
日本語の概要は準備中です。原文の説明を表示しています。
Build and sharpen a project's domain model. Use only when actively changing glossary or ubiquitous-language terms, or recording a durable architectural decision; merely reading a glossary is not a trigger.
日本語の概要は準備中です。原文の説明を表示しています。
Explicit-only interview loop for stress-testing a plan, decision, or idea. Use only when the user asks to grill, interrogate, interview, or stress-test their thinking before action.
日本語の概要は準備中です。原文の説明を表示しています。