Skip to content
cccskills
FreePublished on GitHub

honey-review

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

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

honey

Free

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.

The English summary is being prepared. Showing the original description.

Green-PT/honey-for-devs342Updated Oct 18, 2026

honey

Free

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

The English summary is being prepared. Showing the original description.

Green-PT/honey-for-devs342Updated Oct 18, 2026

honey

Free

Write less code and say less about it. Cuts token cost.

The English summary is being prepared. Showing the original description.

Green-PT/honey-for-devs342Updated Oct 18, 2026

Compress-cache-retrieve huge array tool output.

The English summary is being prepared. Showing the original description.

Green-PT/honey-for-devs342Updated Oct 18, 2026

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

The English summary is being prepared. Showing the original description.

Green-PT/honey-for-devs342Updated Oct 18, 2026

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.

The English summary is being prepared. Showing the original description.

Green-PT/honey-for-devs342Updated Oct 18, 2026

See all skills by Green-PT

Report a problem with this skill