免费在 GitHub 公开

honey-debt

Harvest honey shortcut markers into a debt ledger.

中文简介正在准备中。当前显示原文说明。

Green-PT/honey-for-devs

查看安装方法

包含的文件（1）

SKILL.md1.8 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

Honey Debt

Lever 1 trades code for a known ceiling. That trade is only honest if someone can see it later. Every deliberate simplification carries a shortcut: comment naming its ceiling and the trigger to revisit; this collects them into one ledger. Older code may carry the previous honey: prefix — same convention, harvest both.

Scan

P='(#|//|--|/\*) ?(shortcut|honey):'
if git rev-parse --git-dir >/dev/null 2>&1; then git grep --untracked -nE "$P"
else grep -rnE "$P" . --exclude-dir={node_modules,.git,dist,build,vendor}; fi

Each hit is one row. git grep skips everything gitignored. The comment prefix is what 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>. trigger: <when to revisit>.

The convention is shortcut: <ceiling>, <trigger>, so both fields come straight from the comment. Add git blame -L<line>,<line> -- <file> per row only if the user asks who owns it.

Tag any marker with no trigger no-trigger — a ceiling without a revisit condition is the shape that rots. End with:

<N> markers, <M> with no trigger.

Nothing found: No shortcut debt. Clean ledger.

Boundaries

Report only. Don't fix, refactor, or remove markers — the user decides what to pay down. Offer, don't act.
Don't invent debt. A TODO/FIXME is not a shortcut: marker; mention the count separately at most once if it's large, don't fold it into the ledger.
Don't editorialise per row. The ledger is data. Save any judgement for one closing line, and only if something is genuinely alarming.

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能

honey

免费

Write less code and say less about it. Applies YAGNI and stdlib/native-first so the agent writes the minimum code that needs to exist, and responds tersely — stripping filler, hedging, and pleasantries while keeping code, identifiers, and technical terms exact. Use whenever writing, modifying, refactoring, reviewing, or explaining code, or any response where output volume drives token cost — even if the user never says "minimal" or "concise". Especially in agentic coding, where the volume of generated code and prose runs up the bill.

中文简介正在准备中。当前显示原文说明。