원클릭으로 Manus에서 모든 스킬 실행

시작하기

honey-review

스타173

포크8

업데이트2026년 6월 23일 04:57

Review a diff for over-engineering and verbosity. Terse delete-list of what to cut and the lines each saves. One-shot.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

Green-PT

Green-PT/honey-for-devs

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

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

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

Ordered by lines saved, deepest first.
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:

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

이 저장소의 다른 Skills

같은 저장소

honey-ccr

Green-PT/honey-for-devs

Compress-Cache-Retrieve huge repetitive array tool output before it hits context: keep a sample, cache the rest, leave a hash.

2026-07-12173

honey-ccr

Green-PT/honey-for-devs

Compress-Cache-Retrieve for huge, repetitive array tool output (logs, scan results, time series, event streams) before it enters context. Keeps an informative sample — endpoints, anomalies/change-points, head/tail — drops the redundant rest to a local cache, and leaves a retrievable hash. Use when a tool returns a long uniform JSON array you must read but mostly skim, and the full set is one command away if needed. Lossy-but-recoverable.

2026-07-12173

honey

Green-PT/honey-for-devs

Write less code and say less about it: YAGNI, stdlib-first, terse prose. Cuts agent token cost on every coding and writing task.

2026-07-05173

honey

Green-PT/honey-for-devs

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.

2026-07-05173

honey-chat

Green-PT/honey-for-devs

Honey for plain Claude — the terse-prose core with no agent-harness features. Paste into a claude.ai Project's custom instructions, a Style, or an API system prompt. Strips filler, hedging, and pleasantries from every response while keeping facts, names, numbers, steps, and code exact. No tools required.

2026-07-05173

honey-px

Green-PT/honey-for-devs

Read huge dense read-only text as PNG pages via pxpipe export: ~60-75% fewer input tokens. Lossy on exact strings; never for files you will edit.

2026-07-05173

name	honey-review
description	Review a diff for over-engineering and verbosity. Terse delete-list of what to cut and the lines each saves. One-shot.
homepage	https://github.com/Green-PT/honey-for-devs
license	MIT

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)

Output — delete-list, one line per finding

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

Ordered by lines saved, deepest first.
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:

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