bounty-board — Claude Code plugin: tech debt as aging XP rewards
bounty-board turns TODO and FIXME comments into bounties that grow in XP value as they age. Scans your repo, prices each debt marker by git-blame age, and feeds the top 3 into your session as side quests.
MIT ★ 586 updated 2026-10-26
/plugin marketplace add karanb192/claude-code-hooks
/plugin install bounty-board@claude-code-hooksWhat bounty-board does
bounty-board runs on three hooks. At SessionStart, it scans git-tracked files for TODO, FIXME, HACK, XXX, BUG, skipped tests, and suppressed linters. Each gets priced in XP: older markers pay more, based on git-blame history. The board renders and the top 3 bounties inject into context as side quests.
After you edit a file, a PostToolUse hook re-checks it. If a marker verifiably vanishes, the bounty pays out. Rewording keeps the bounty open (transferred instead of paid); renaming the file doesn't trigger payout. At SessionEnd, it renders a payout card: XP earned, bounties cleared, burn-down of what remains.
Scanning caps itself at 400 files and 256 KB per file, finishing in about 1.8 seconds. All state lives in ~/.claude/bounty-board/ as JSON; no network calls, no dependencies beyond Node.js built-ins.
What it helps with
- prioritize tech debt across a large codebase without manual audits
- surface the oldest, highest-value TODOs that have been neglected
- incentivize clearing debt markers during focused coding sessions
- verify which comments actually disappeared after an edit
Example prompts for the agent
- Start a session — bounty-board scans and shows the top 3 high-value tasks in context
- Edit a file and delete an old TODO — the hook checks and awards XP if the marker is truly gone
- Run
/bounty-board:boardanytime to see the live board and highest-paying bounties
How to install bounty-board
Plugin marketplace
/plugin marketplace add karanb192/claude-code-hooks/plugin install bounty-board@claude-code-hooksStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about bounty-board
How do I install bounty-board in Claude Code?
Run /plugin marketplace add karanb192/claude-code-hooks, then /plugin install bounty-board@claude-code-hooks. Restart Claude Code.
What does bounty-board do?
It scans your code for TODO, FIXME, HACK and other debt markers, assigns XP based on how long each has existed in git history, displays the board, and automatically awards XP when you remove a marker.
Is data stored locally and does it need network access?
All state is stored locally in ~/.claude/bounty-board/ as JSON files. The hook makes no network calls and relies only on Node.js built-in modules.
Source text
bounty-board · MIT
# bounty-board > Prices your repo's TODO/FIXME/HACK debt as aging XP bounties, injects the top 3 as opportunistic side quests, and verifies + pays out the bounties you genuinely clear. On SessionStart it scans your git-tracked files, matches comment markers (TODO/FIXME/HACK/XXX/BUG), skipped tests, and lint suppressions, and prices each as a "wanted poster" bounty whose XP scales with git-blame age and severity: older debt pays more. It renders the board as a card and injects the top 3 as side quests via `additionalContext`. A PostToolUse hook re-checks touched files after each edit and pays out bounties whose markers verifiably disappear (rewording transfers the bounty instead of paying; a rename never pays). SessionEnd renders a payout card: XP earned, bounties cleared, and the remaining burn-down. Scanning is cost-bounded (400 files, 256KB/file, ~1.8s total) so it stays cheap on large repos. ## Install ``` /plugin marketplace add karanb192/claude-code-hooks # once per machine /plugin install bounty-board@claude-code-hooks ``` Restart Claude Code, done. (Or from a shell: `claude plugin install bounty-board@claude-code-hooks`.) ## What it does | Event | Runs | What happens | | --- | --- | --- | | SessionStart | sync | Scans tracked files, prices each TODO/FIXME/HACK/skip/lint-suppression as an aging bounty, renders the board, and injects the top 3 as side quests via `additionalContext`. Re-fires on resume/compact without resetting earnings. | | PostToolUse (`Edit\|MultiEdit\|Write\|NotebookEdit\|Bash`) | sync | After a file is touched, re-checks that file's bounties and pays out any whose marker verifiably disappeared (verify-then-reward). Sync because it returns an `additionalContext` payout message. | | SessionEnd | sync | Renders the payout card: XP earned this session, bounties cleared, and the remaining board burn-down. | `/bounty-board:board` renders the current bounty board on demand and calls out the fattest open bounties. ## Configuration No configuration needed. State is stored under `~/.claude/bounty-board/` (one JSON ledger per repo); hook logs go to `~/.claude/hooks-logs/`. ## Data & privacy For each bounty it records the marker text, file path, line, git-blame age, and XP in a local JSON ledger. Everything stays on your machine: the hook makes no network calls (Node built-ins only, zero dependencies). ## Uninstall ``` /plugin uninstall bounty-board@claude-code-hooks ```
© Karan Bansal · MIT · karanb192/claude-code-hooks