A coding command that fetches a GitHub issue, finds the related code, writes a test, implements a fix, and opens a pull request. A GitHub issue is a tracked bug or task, and a pull request proposes code changes for review.

Use it with an issue number to investigate and fix a GitHub issue, run the relevant tests, and prepare the change for review.

It turns the usual issue-fixing steps into one guided workflow. This helps keep the fix tied to the reported problem and checked by a test.

How kimrejstrom/alpacalyzer-algo-trader configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to kimrejstrom/alpacalyzer-algo-trader. 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/kimrejstrom/alpacalyzer-algo-trader/main/.agents/commands/fix-issue.md

Clone the repo

git clone --depth 1 https://github.com/kimrejstrom/alpacalyzer-algo-trader

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/kimrejstrom/alpacalyzer-algo-trader/fix-issue/github.svg)](https://agentmods.dev/commands/kimrejstrom/alpacalyzer-algo-trader/fix-issue)

Your own site

<a href="https://agentmods.dev/commands/kimrejstrom/alpacalyzer-algo-trader/fix-issue"><img src="https://agentmods.dev/badge/commands/kimrejstrom/alpacalyzer-algo-trader/fix-issue/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/kimrejstrom/alpacalyzer-algo-trader/fix-issue"><img src="https://agentmods.dev/badge/commands/kimrejstrom/alpacalyzer-algo-trader/fix-issue.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 609 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.00609
Opus 5.5	$0.00000	$0.00244
Sonnet 5.5	$0.00000	$0.00122
Haiku 4.5	$0.00000	$0.00061

Measured 2mo ago against content hash f393742c851d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

.agents/commands/fix-issue.md · 143 lines

How it starts

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

Fix Issue Command

Fetch issue details, find relevant code, implement fix, and open PR.

Usage

/fix-issue <issue_number>

Arguments:

issue_number: The GitHub issue number to fix

Argument Indexing

Claude Code: Use $1 for the first argument (issue number)
OpenCode: Use $ARGUMENTS to get all arguments

Steps

1. Get Repo Info

git remote get-url origin

Parse owner and repo name.

2. Fetch Issue

Use gh CLI to fetch the issue:

gh issue view <issue_number> --repo <owner>/<repo>

3. Analyze Issue

Read the issue description:

What needs to be fixed?
What are the acceptance criteria?
Are there any hints about where the code lives?

4. Find Relevant Code

Search for relevant code:

# Search for keywords
rg "keyword" src/

# Find test files
ls tests/test_*.py

5. Create Branch

git checkout -b fix/issue-<issue_number>-<short-description>

6. Write Test First

Create test that reproduces the issue:

def test_bug_fix():
    """Test for issue #XX"""
    # Test that demonstrates the bug
    pass

Run test to confirm it fails.

7. Implement Fix

Implement the fix to make the test pass.

8. Run Tests

uv run pytest tests -x -q

9. Run Linting

uv run ruff check .
uv run ruff format .

10. Run Type Checking

uv run ty check src

11. Commit

git add -A
git commit -m "fix(scope): description for #XX"

12. Push and Create PR

git push -u origin fix/issue-XX-description

gh pr create --repo <owner>/<repo> \
  --title "fix(scope): description for #XX" \
  --head fix/issue-XX-description \
  --base main \
  --body-file - <<'EOF'
## Summary
<description>

## Issue
Fixes #XX
EOF

13. Trigger Code Review

@code-reviewer Please review:
- ISSUE_NUMBER: <issue_number>
- PR_NUMBER: <pr_number>
- OWNER: <owner>
- REPO: <repo>
- FEATURE_DESCRIPTION: <brief description>

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

2mo ago First seen · 143 lines · 0 tokens per session scan A f393742c851d

Subscribe to this mod's changes

fix-issue is a command published in the GitHub repository kimrejstrom/alpacalyzer-algo-trader (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 609 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-31.

Debugging Git and workflow

fix-issue next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
fix-issuekimrejstrom/alpacalyzer-algo-trader	Command	2	5mo ago	MIT	A	0	Claude Code
barista-fixfrappe/frappe-ui	Command	1.1k	2d ago	MIT	A	17	Claude Code
fix-issueyonatangross/orchestkit	Command	299	yesterday	MIT	A	45	Claude Code, Cursor
unbloatathola/claude-night-market	Command	348	yesterday	MIT	A	27	Claude Code
payload-revertopenshift-eng/ai-helpers	Command	122	yesterday	Apache-2.0	A	12	Claude Code
AGENTSmax-sixty/worktrunk	Command	12k	yesterday	none	A	0	Claude Code
fix-issuefltman/project-scaffolder	Command	88	9d ago	MIT	A	0	Claude Code

alpacalyzer-algo-trader: Command for Claude Code