/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
Claude Code
$ npx -y skills add Green-PT/honey-for-devs --skill honey-debt --agent claude-code
Codex
$ npx skills add Green-PT/honey-for-devs --skill honey-debt -a codex -y
Cursor
$ npx skills add Green-PT/honey-for-devs --skill honey-debt -a cursor -y
Gemini CLI
$ npx skills add Green-PT/honey-for-devs --skill honey-debt -a gemini-cli -y
GitHub Copilot
$ npx skills add Green-PT/honey-for-devs --skill honey-debt -a github-copilot -y
OpenCode
$ npx skills add Green-PT/honey-for-devs --skill honey-debt -a opencode -y
Windsurf
$ npx skills add Green-PT/honey-for-devs --skill honey-debt -a windsurf -y
SKILL.md
honey-debt.SKILL.mdname: honey-debt
description: >-
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.
license: MIT
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}; fiEach 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.
Read more
name: honey-debt description: >- 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. license: MIT
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}; fiEach 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.
Write less code and say less about it. Honey (I Shrunk the AI) by GreenPT is a cross-tool coding skill that cuts the output tokens AI coding agents spend — making them emit less code and less prose without losing correctness.
Other skills on honey.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about honey-debt.
- Which coding agents can use honey-debt?
- honey-debt installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

