From bounty-board
Displays a bounty board of TODO/FIXME/HACK debt items priced as XP bounties based on git-blame age. Helps prioritize technical debt by surfacing the oldest, highest-value items.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bounty-board:boardThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
!`node "${CLAUDE_SKILL_DIR}/../../bounty-board.js" --render 2>/dev/null || node "${CLAUDE_PLUGIN_ROOT}/bounty-board.js" --render`
!node "${CLAUDE_SKILL_DIR}/../../bounty-board.js" --render 2>/dev/null || node "${CLAUDE_PLUGIN_ROOT}/bounty-board.js" --render
The card above is this repository's open bounties — each TODO/FIXME/HACK/skip/lint-suppression
priced as a wanted-poster bounty whose XP scales with its git-blame age (older debt = fatter
bounty). It is produced by the bounty-board hook, which scans the repo on demand.
Briefly call out the 1–3 fattest bounties and, for each, name the file:line and what it would take to genuinely clear it (resolve the debt, not just delete the marker). Keep it short; do not re-run any commands.
npx claudepluginhub karanb192/claude-code-hooks --plugin bounty-boardHarvests every `ponytail:` comment into a debt ledger, tracking deliberate shortcuts. One-shot report, no changes. Activate via 'ponytail debt' or '/ponytail-debt'.
Inventories, quantifies, and prioritizes technical debt into a ranked register by interest over principal. Covers code smells, dependency debt, test gaps, and churn hotspots. Files GitHub issues on request.
Identifies, categorizes, and prioritizes technical debt across seven dimensions with remediation plans and effort estimates. Useful for refactoring track planning.