A command that creates a step-by-step remediation plan for a reported software bug. The plan is saved as a Markdown file in a specified project cache directory and is intended for another agent to implement.

Use it to prepare plans for GitHub issues, including the affected area, priority, effort, status, and the files or steps needed to fix the defect.

It turns an issue report into a focused implementation plan while checking required issue labels and avoiding unnecessary file changes.

How jayminwest/kotadb configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to jayminwest/kotadb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/jayminwest/kotadb/develop/.claude/commands/issues/bug.md

Clone the repo

git clone --depth 1 https://github.com/jayminwest/kotadb

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/jayminwest/kotadb/bug/github.svg)](https://agentmods.dev/commands/jayminwest/kotadb/bug)

Your own site

<a href="https://agentmods.dev/commands/jayminwest/kotadb/bug"><img src="https://agentmods.dev/badge/commands/jayminwest/kotadb/bug/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/jayminwest/kotadb/bug"><img src="https://agentmods.dev/badge/commands/jayminwest/kotadb/bug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,324 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01324
Opus 5.5	$0.00000	$0.00530
Sonnet 5.5	$0.00000	$0.00265
Haiku 4.5	$0.00000	$0.00132

Measured 1mo ago against content hash 6391538e6ebb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

bug scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

refactor — 86% identical, 104 lines differ

.claude/commands/issues/bug.md · 121 lines

How it starts

The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/bug

Template Category: Action

Author a remediation plan for the bug described in $ARGUMENTS (issue metadata JSON). The plan must equip the implementor to fix the defect with minimal churn.

CRITICAL - Worktree Path Handling:

You are executing in an isolated git worktree directory
Your CWD is the worktree root (e.g., /project/trees/bug-123-abc12345)
ALL file paths in Write, Edit, Read tools MUST be relative to CWD
✅ Correct: .claude/.cache/specs/bug-123-plan.md
❌ Wrong: /project/trees/bug-123-abc12345/.claude/.cache/specs/bug-123-plan.md
Using absolute paths will cause git staging failures and commit errors

Instructions

Verify issue labels first: Run gh issue view <issue-number> --json labels to ensure the issue has labels from all four categories (component, priority, effort, status). If labels are missing, apply them before proceeding.
Create a new markdown plan under .claude/.cache/specs/ named bug-<issue-number>-<slug>.md (e.g., .claude/.cache/specs/bug-2210-missing-search-results.md).
Build <slug> from the issue title using 3–6 lowercase, hyphenated words (alphanumeric only).
Follow the format exactly so orchestrators can parse sections reliably.
Use KotaDB MCP tools for discovery: Use mcp__kotadb-staging__search_code to find related error handling code, mcp__kotadb-staging__search_dependencies for impact assessment (see .claude/commands/docs/kotadb-agent-usage.md for patterns)
Reproduce the bug mentally using the provided context and outline how to confirm both failure and resolution.
Investigate impacted modules in src/**, tests/**, and any infrastructure noted in the issue before proposing changes.
Capture all impacted files (and any new assets) in the dedicated section so implementors have clear scope boundaries.
Reference the repo git flow: work from bug/<issue-number>-<slug> off develop, with develop promoted to main on release.
Integrate /anti-mock expectations: propose real database test coverage, failure injection, and follow-ups for any temporary skips.
Ensure the plan's closing tasks rerun validation and push the branch so a PR can be raised (PR titles must end with the issue number, e.g. fix: correct row filters (#210)).
Consult .claude/commands/docs/conditional_docs/app.md or .claude/commands/docs/conditional_docs/automation.md and read only the documentation whose conditions align with the defect.
When the remediation introduces new documentation, add or update the relevant conditional entry so future agents can discover it quickly.

Read the full file on GitHub · 121 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 121 lines · 0 tokens per session scan A 6391538e6ebb

Subscribe to this mod's changes

bug is a command published in the GitHub repository jayminwest/kotadb (100 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,324 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code Debugging ai-tools mcp

kotadb: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

How it starts

/bug

Instructions

What this file has done since we first saw it

Other commands, from other repositories

async-check

type-coverage

debug

statusbar-doctor

coolify-debug

umt-doctor