lean-debt
Skill8 starsChanged 3 months agoApache-2.0View on GitHub
Harvest every `lean:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals Lean leaves behind get tracked instead of rotting into "later means never". Use when the user says "lean debt", "/lean-debt", "what did lean defer", "list the shortcuts", "lean ledger", or "what did we mark to do later". One-shot report, changes nothing.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- FareedKhan-dev/lean-agenttheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- FareedKhan-dev/lean-agent★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- .cursor/rules/ponytail.mdcCursor rule
- compressSkill
- lean-auditSkill
- lean-commitSkill
- lean-gainSkill
- lean-helpSkill
- lean-reviewSkill
- leanSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Every deliberate Lean shortcut is marked with a lean: comment naming its ceiling and upgrade path.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Every deliberate Lean shortcut is marked with a lean: 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 '(#|//) ?lean:' . (add other comment prefixes if your stack uses them)
Each hit is one ledger row. The space and comment prefix keep 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 lean: <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 lean: 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 lean: debt. Clean ledger.
Boundaries
Reads and reports only, changes nothing. To persist it, ask and it writes the
ledger to a file (e.g. LEAN-DEBT.md). One-shot. "stop lean-debt" or
"normal mode" to revert.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.