An end-to-end command for resolving a GitHub or Linear issue, from reading its requirements through creating a pull request.

It fetches issue details and recent comments, creates a branch, plans the fix or feature, implements it, verifies the result, and prepares a pull request.

It organizes issue work so the requirements, acceptance criteria, implementation plan, code changes, tests, and review are handled in sequence.

fix-issue — Command for Claude Code by llcoolblaze: An end-to-end command for resolving a GitHub or Linear…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/llcoolblaze/claude-boris/fix-issue

Clone the repo

git clone --depth 1 https://github.com/llcoolblaze/claude-boris

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/llcoolblaze/claude-boris/fix-issue.svg)](https://agentmods.dev/commands/llcoolblaze/claude-boris/fix-issue)

Your own site

<a href="https://agentmods.dev/commands/llcoolblaze/claude-boris/fix-issue"><img src="https://agentmods.dev/badge/commands/llcoolblaze/claude-boris/fix-issue.svg" alt="Measured on agentmods" height="20"></a>

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

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

Security scan A 0 findings. Scan, not verified.

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	$0.00026	$0.00683
Opus 5	$0.00013	$0.00342
Sonnet 5	$0.00005	$0.00137
Haiku 4.5	$0.00003	$0.00068

Measured 4d ago against content hash 2a5429b50688, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fix-issue 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 4d 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.

.claude/commands/fix-issue.md · 136 lines

How it starts

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

Fix Issue: $ARGUMENTS

Fetching Issue Details...

!gh issue view $ARGUMENTS --json number,title,body,labels,assignees,state 2>/dev/null || echo "Provide issue number: /fix-issue 123"

Issue Comments (Context)

!gh issue view $ARGUMENTS --json comments -q '.comments[-3:] | .[].body' 2>/dev/null | head -30 || echo ""

Issue Resolution Protocol

1. Parse Issue

Extract from the issue:

Type (from labels):

bug - Something broken
feature - New functionality
enhancement - Improve existing
documentation - Docs only

Acceptance Criteria:

Look for checkboxes
Look for "should" statements
Look for code examples

2. Create Branch

ISSUE_NUM=$ARGUMENTS
SLUG=$(gh issue view $ISSUE_NUM --json title -q '.title' | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | cut -c1-40)

git checkout main && git pull origin main
git checkout -b "issue-$ISSUE_NUM-$SLUG"

3. Plan Implementation

Create a plan before coding:

What's the root cause (for bugs)?
What files need to change?
What tests are needed?
Any risks or edge cases?

Get user approval on plan before proceeding.

4. Implement

Make changes incrementally
Follow existing code patterns
Add tests for new code
Update documentation if needed

5. Verify

npm test
npm run typecheck
npm run lint
npm run build

All checks must pass.

6. Commit & PR

git add -A
git commit -m "fix: [description]

Fixes #$ARGUMENTS"

git push -u origin HEAD

gh pr create \
  --title "Fix #$ARGUMENTS: [title]" \
  --body "## Summary
Fixes #$ARGUMENTS

## Changes
- [What changed]

## Testing
- [How tested]"

7. Update Issue

gh issue comment $ARGUMENTS --body "PR created. Ready for review."
gh issue edit $ARGUMENTS --add-label "in-review"

Output Format

## Issue #[num] Complete

**Title**: [title]
**Type**: [bug/feature]
**Branch**: issue-[num]-[slug]

### Changes Made
- [Description]

### Verification
- ✅ Tests pass
- ✅ Types check
- ✅ Lint clean

### PR Created
#[PR] - [title]

Read the full file on GitHub · 136 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.

4d ago First seen · 136 lines · 26 tokens per session scan A 2a5429b50688

Subscribe to this mod's changes

fix-issue is a command published in the GitHub repository llcoolblaze/claude-boris (48 stars, last pushed 7mo ago), licensed MIT. It adds 26 tokens to every session and 683 once invoked, about $0.0001 per session on Opus 5. 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.

Git and workflow Project management

fix-issue