Harvest every ponytail: shortcut comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.
12 installs
Documents
ken-debt
Try itHarvest every ken: ceiling comment into one ledger, so brute-force deferrals get tracked instead of forgotten. One-shot report.
What it does
Harvest every ken: ceiling comment into one ledger, so brute-force deferrals get tracked instead of forgotten. One-shot report.
The skill document
Every deliberate ken brute-force ceiling is marked with a ken: comment
naming its ceiling and upgrade trigger. This collects them into one ledger so
a deferral can't become permanent without notice.
Scan
Grep the repo for comment markers, skipping node_modules, .git, and build
output:
grep -rnE '(#|//) ?ken:' . (add other comment prefixes if your stack uses them)
Each hit is one ledger row. The comment prefix keeps prose that mentions the convention out of the ledger.
Output
One row per marker, grouped by file:
:, . ceiling: . upgrade: .
The convention is ken: , , so pull the ceiling
and the trigger straight from the comment. Want an owner per row too? add
git blame -L,.
Flag the rot risk: any ken: comment that names no upgrade trigger gets a
no-trigger tag; those can rot without warning.
End with markers, with no trigger. Nothing found: No ken: debt. Clean ledger.
Boundaries
Reads and reports only, changes nothing. To persist it, ask and it writes the
ledger to a file (e.g. KEN-DEBT.md). One-shot. "stop ken-debt" or
"normal mode" to revert.
Related skills
Show ken measured impact as a scoreboard from its own benchmark results. Honest empty state when none exist. One-shot display.
Quick reference for ken modes, skills, and commands. One-shot display.
Thompson-mode discipline for any coding task: think first, build bottom-up, brute force until measured, rewrite over patch. Not for non-coding requests.
Review a diff for method violations: rot to rewrite, translate-only layers, unvouched deps, fancy over brute force. One line per finding.
Audit the whole repo for Thompson-mode violations. A ranked list of what to rewrite, delete, or take back into the trusted base.