免费在 GitHub 公开

honey-review

Review a diff for what Honey would cut — over-engineering (speculative generality, hand-rolled stdlib, single-caller abstractions) and over-verbosity (dead code, narration, redundant comments). Outputs a terse delete-list, one line per finding, with the line count each cut saves. Use when asked to review, trim, or de-bloat a change, or before opening a PR. Quality lever only — it finds waste, not correctness bugs.

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

Green-PT/honey-for-devs

实测评分未实测

查看安装方法

包含的文件（1）

SKILL.md2.0 KB

SKILL.md（原文）

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

Honey Review

Read the diff (git diff or the named range). Report only what to cut and why — the reverse of Honey's two write-levers.

Find

Over-engineering (Lever 1) — code that needn't exist: speculative params, "might need it later" branches, single-caller abstractions, hand-rolled itertools/pathlib/datetime, a new dependency for four lines, a reimplemented existing util.
Over-verbosity (Lever 2) — dead code, commented-out blocks, comments narrating what the code already says, redundant scaffolding.

Never flag (the carve-out is load-bearing)

Input validation, error handling, auth, secrets handling, accessibility basics, and visual/UX polish on user-facing deliverables are not bloat. A test or assert proving non-trivial logic is not bloat. Don't suggest cutting them.

Output — delete-list, one line per finding

N. path:line — cut <what>; <one-clause why> (−N lines)

Numbered and ordered by lines saved, deepest first, so the user can answer "cut 1 and 3".
End with one total line: Total: −N lines across M findings.
Nothing to cut → say so in one line. Don't manufacture findings.
Terse but human-readable (this is for a person, not an agent — that's hive-reviewer's job).

Example:

1. src/util.py:12 — cut hand-rolled flatten; stdlib itertools.chain.from_iterable does it (−9 lines)
2. src/api.js:40 — cut unused `opts` param; no caller passes it (−3 lines)
Total: −12 lines across 2 findings.

评价

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

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

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

同一仓库的技能

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.

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