agentmods.dev

fix-github-issue

fix-github-issue is a skill for Claude Code from simiancraft/simiancraft-skills. It costs 161 tokens per session (1,658 once invoked), scanned A, original, MIT.

An automated workflow that turns one known GitHub issue into a proposed and potentially merged code change. It works in a separate Git worktree, creates a draft pull request, runs an isolated review, and repeatedly revises or stops according to the outcome.

In plain words
What is it for?
Use it to implement one issue without an interactive coding session, attach proof to a draft pull request, obtain a second-engine review, and merge only after the configured checks pass.
Why use it?
It keeps implementation, review, and merging separate and records why work was merged, parked, handed off, or stopped. Checking the base code before merging helps detect changes that made the proposed fix stale.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Codex.

Part of the simiancraft-skills plugin — 21 skills, 4 agents shipped together

not rated 8repo 5d ago A scan 161 tokens original MIT

Good fit Use it to implement one issue without an interactive coding session, attach proof to a draft pull request, obtain a second-engine review, and merge only after the configured checks pass.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/simiancraft/simiancraft-skills/fix-github-issue
View source ↗ simiancraft/simiancraft-skills
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.

Any agent
npx skills add simiancraft/simiancraft-skills --skill fix-github-issue
Clone the repo
git clone --depth 1 https://github.com/simiancraft/simiancraft-skills

Made for: Claude Code.

Or install simiancraft-skills, the plugin that ships this one along with the rest of its 21 skills, 4 agents.

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.

agentmods badge for fix-github-issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/simiancraft/simiancraft-skills/fix-github-issue/github.svg)](https://agentmods.dev/skills/simiancraft/simiancraft-skills/fix-github-issue)
Your own site
<a href="https://agentmods.dev/skills/simiancraft/simiancraft-skills/fix-github-issue"><img src="https://agentmods.dev/badge/skills/simiancraft/simiancraft-skills/fix-github-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.

agentmods 80×15 button for fix-github-issue

Your own site · 80×15
<a href="https://agentmods.dev/skills/simiancraft/simiancraft-skills/fix-github-issue"><img src="https://agentmods.dev/badge/skills/simiancraft/simiancraft-skills/fix-github-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 161 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,658 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00161 $0.01658
Opus 5.5 $0.00064 $0.00663
Sonnet 5.5 $0.00032 $0.00332
Haiku 4.5 $0.00016 $0.00166

Measured 5d ago against content hash ef12b9a90587, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

fix-github-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 5d ago.

The scan reads SKILL.md. This mod also ships 36 executable files (fix.ts, fix.usage.test.ts, lib/agent.timeout.test.ts, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/fix-github-issue/SKILL.md · 112 lines

How it starts

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

Fix GitHub Issue

One issue in, one outcome out: merged, parked, handed-off, closed, dlq, or failed when it ran, and left-alone, busy, not-run, stopped, or lease-lost when it did not settle the issue (references/pipeline.md says what each means). Internally it is a worker, then a review, then a landing, revising until the issue's review budget is spent.

Invoked by burn-down-github-issues (one call per Ready card) and walk-the-floor (the repair after an incident), both through fixIssue.

The pipeline is shared; the repository is config. Nothing here is copied into a repository. Everything true of a repository (remotes, branches, commands, path aliases, invalidation paths) lives in a config file at that repository's root, and the pipeline refuses to start without one, naming the missing file and the fields it lacks.

Every stage takes an explicit context rather than reading module state, so one process can run two pipelines against two configurations without either seeing the other's queue, seats (the roles an agent fills: worker, reviewer, confirmer), or run directory. That is what makes fixIssue callable as the fix seat of a larger loop.

When to use it

  • One issue you already believe is real and small enough, to be fixed unattended.
  • As the fix stage of another driver: import lib/pipeline.ts and call fixIssue(ctx, issue, { maxPoints }), building the context with lib/context.ts.

Skip it for an issue you are working interactively, for anything blocked on a product decision, and for work whose remedy is a judgement call rather than a change.

Run it

From inside the target repository (any directory of it, including a worktree):

bun run <this-skill-dir>/fix.ts --issue <n>
bun run <this-skill-dir>/fix.ts --issue <n> --dry-run
bun run <this-skill-dir>/fix.ts --issue <n> --max-points 8   # raise the size ceiling for this issue only
bun run <this-skill-dir>/fix.ts --issue <n> --worker codex:gpt-5.6-sol --reviewer claude:claude-opus-5
bun run <this-skill-dir>/fix.ts --issue <n> --confirmer claude:claude-opus-5   # the seat that re-checks a close the worker proposes
bun run <this-skill-dir>/fix.ts --issue <n> --redrive        # lift a park or a dead letter and continue the issue's pull request
bun run <this-skill-dir>/fix.ts --issue <n> --resume-pr <pr> # continue that open pull request rather than open another

Read the full file on GitHub · 112 lines

Files

What ships with it

40 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 5d ago First seen · 112 lines · 161 tokens per session scan A ef12b9a90587

Subscribe to this mod's changes

fix-github-issue is a skill published in the GitHub repository simiancraft/simiancraft-skills (8 stars, last pushed 5d ago), licensed MIT. It adds 161 tokens to every session and 1,658 once invoked, about $0.0006 per session on Opus 5.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-10-20.

Code reviewCommitsGit and workflowagent-skillsai-agentsclaudeclaude-code-marketplaceclaude-code-plugin
Related

Other skills, from other repositories

avi-pr-flow

Automate PR workflow with commit, push, create PR, and review cycle.

avi1234/claude-team-plugins · 15 tokens

pr-review

Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.

oliver-kriska/claude-elixir-phoenix · 59 tokens

phx-pr-review

Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.

oliver-kriska/claude-elixir-phoenix · 61 tokens

signing-preflight

Before the first commit of a session, check that commit signing will work — the key is loaded and unlocked — and ask the operator to unlock it once, up front, instead of discovering it after a hundred unsigned commits. Never disables signing silently, never re-signs history without asking. Use at the start of…

avelikiy/great_cto · 105 tokens

pr-review

Review pull requests and Git diffs with Graph-It-Live risk, breaking-change, dependency-impact, cycle, unused-export, and test-candidate evidence. Use when asked to review a PR, inspect a diff, assess merge risk, check a branch before merging, create a Graph-It-Live review gate, or explain review-pr results. Trigger…

magic5644/Graph-It-Live · 132 tokens

loop-gh-pr

A recipe for a scheduled GitHub pull-request watcher. It checks open pull requests for new activity and prepares read-only review drafts without posting comments or merging anything.

restarter/lets-workflow · 118 tokens