Skip to content
cccskills
FreePublished on GitHub

honey-debt

Harvest every `shortcut:` comment (and legacy `honey:` ones) in the codebase into a debt ledger, so the deliberate shortcuts Lever 1 leaves behind get tracked instead of rotting into "later means never". Flags markers with no revisit trigger — those are the ones that go permanent silently. Use when the user says "honey debt", "/honey-debt", "what did honey defer", "list the shortcuts", or "what did we mark to do later". One-shot report; changes nothing.

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

See how to install

Files included (1)

  • SKILL.md2.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

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 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

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

See all skills by Green-PT

Report a problem with this skill