fix-review

fix-review is a command for Claude Code from GabsFranke/claude-code-github-agent. It costs 11 tokens per session (2,374 once invoked), scanned A, original, MIT.

A command that reads comments left on a pull request, which is a proposed code change, and applies the requested fixes with delegated agent help.

In plain words
What is it for?
Use it after a pull-request review to address reviewer feedback and update the code.
Why use it?
It reduces the manual work of turning review comments into code changes.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions subagents.

Part of the pr-fix plugin — 1 command shipped together

Good fit Use it after a pull-request review to address reviewer feedback and update the code.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/gabsfranke/claude-code-github-agent/fix-review
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.

Clone the repo
git clone --depth 1 https://github.com/GabsFranke/claude-code-github-agent

Made for: Claude Code.

Or install pr-fix, the plugin that ships this one along with the rest of its 1 command.

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-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/gabsfranke/claude-code-github-agent/fix-review/github.svg)](https://agentmods.dev/commands/gabsfranke/claude-code-github-agent/fix-review)
Your own site
<a href="https://agentmods.dev/commands/gabsfranke/claude-code-github-agent/fix-review"><img src="https://agentmods.dev/badge/commands/gabsfranke/claude-code-github-agent/fix-review/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-review

Your own site · 80×15
<a href="https://agentmods.dev/commands/gabsfranke/claude-code-github-agent/fix-review"><img src="https://agentmods.dev/badge/commands/gabsfranke/claude-code-github-agent/fix-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,374 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.00011 $0.02374
Opus 5.5 $0.00004 $0.00950
Sonnet 5.5 $0.00002 $0.00475
Haiku 4.5 $0.00001 $0.00237

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

Security

Grade A, and why

fix-review 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.

plugins/pr-fix/commands/fix-review.md · 324 lines

How it starts

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

Fix PR Review Feedback

Read all review feedback from a PR, build a fix plan, delegate implementation to agents, and create a PR with the fixes.

Arguments: "$ARGUMENTS"

  • First argument: Repository (owner/repo format, required)
  • Second argument: PR number (required)

Your Role as Orchestrator

You coordinate the entire process. Your responsibilities:

  1. Create a branch for the fix work
  2. Fetch all review feedback from the PR
  3. Parse and deduplicate findings
  4. DELEGATE implementation to agents (they do ALL the coding)
  5. Run quality checks
  6. Create the PR targeting the original PR's branch
  7. Post summary comment

Key principles:

  • YOU create the branch — use a meaningful name like fix/review-{pr_number}
  • YOU gather and analyze — understand all feedback before delegating
  • YOU NEVER implement fixes yourself — always delegate to agents
  • Agents implement ALL fixes — they work in your branch and commit changes
  • YOU create the PR — after all fixes are committed by agents
  • YOU post the final summary — comprehensive results to GitHub
  • gh CLI is NOT available — use mcp__github__* tools exclusively

Workflow

Step 0: Create a Branch for This Work

CRITICAL: Do this FIRST before any other work!

The worktree starts in detached HEAD state. Create a branch first:

timestamp=$(date +%s)
branch_name="fix/review-${pr_number}-${timestamp}"

git checkout -b "$branch_name"

# Verify
current_branch=$(git branch --show-current)
echo "Created branch: $current_branch"

All agents you invoke will work in this same branch.

Step 1: Parse Arguments

Extract from $ARGUMENTS:

  • Repository (owner/repo)
  • PR number

Step 2: Fetch PR Metadata

Get the PR details to understand what we're working with:

mcp__github__pull_request_read(method="get", owner=<owner>, repo=<repo>, pull_number=<pr_number>)

From this response, extract:

  • head.ref — the PR's feature branch (this is the target for our fix PR)
  • head.sha — the head commit SHA
  • title and body — PR description context
  • changed_files — number of files changed
  • additions / deletions — size of changes

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

  1. 1mo ago First seen · 324 lines · 11 tokens per session scan A 3a835719f05c

Subscribe to this mod's changes

fix-review is a command published in the GitHub repository GabsFranke/claude-code-github-agent (5 stars, last pushed 26d ago), licensed MIT. It adds 11 tokens to every session and 2,374 once invoked, about $0.0000 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-08-31.