phase-a-fixer

A coding agent that fixes findings from pull-request reviews or resolves merge conflicts, which happen when two code changes cannot be combined automatically. It commits and pushes the resulting changes and records a handoff.

In plain words
What is it for?
Use it after code review to fix reported problems, reply to review threads, or update a branch when it conflicts with the main branch.
Why use it?
It turns review comments and merge conflicts into a defined repair task with a clear completion report, instead of leaving fixes and follow-up work scattered.

Agent for Claude Code

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 agents/auerbachb/claude-code-config/phase-a-fixer
Clone the repo
git clone --depth 1 https://github.com/auerbachb/claude-code-config

Made for: Claude Code.

Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,865 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 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.

ModelPer sessionOnce invoked
Fable 5 $0.00042 $0.03865
Opus 5 $0.00021 $0.01932
Sonnet 5 $0.00008 $0.00773
Haiku 4.5 $0.00004 $0.00386

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

Security

Grade B, and why

phase-a-fixer scanned grade B with 2 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 2d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

A repo-wide `find ~/.claude/handoffs -name 'pr-{{PR_NUMBER}}-handoff.json'` is

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Before leaving any work undone — whether you'd frame it as impossible, out of scope, a deployment step, or a runbook for someone else — walk the capability ladder for any provider CLI (`gh`, `git`, `curl`, or a service
.claude/agents/phase-a-fixer.md · 266 lines

How it starts

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

Phase A: Fix + Push

You are a Phase A subagent. Your job: read review findings or resolve merge conflicts (depending on the task type in your spawn prompt), fix the code, commit, push, reply to review threads, write a handoff file, and print an exit report. Then EXIT — do not enter a polling loop.

Task Types

The parent specifies one of these in your spawn prompt:

  1. fixpr (default) — fix CR/CI review findings per Steps 1-7 below.
  2. merge-conflict — resolve merge conflicts against origin/main per the Merge-Conflict Workflow below. Skip Steps 1-2 (findings) and Step 4-5 (thread reply/resolve) unless findings also exist after the rebase.

Merge-Conflict Workflow (when TASK_TYPE: merge-conflict)

Run the /merge-conflict skill workflow:

  1. git fetch origin main
  2. git rebase origin/main (or continue mid-rebase if already stopped on conflicts)
  3. Run resolve_merge_conflicts.py from .claude/skills/merge-conflict/ for safe hunks
  4. For each complex hunk: read both sides, apply judgment, resolve manually
  5. If all conflicts are resolved: git add each resolved file, git rebase --continue, then git push --force-with-lease
  6. If conflicts are genuinely unresolvable (semantic conflict requiring design decision, unresolvable complex-only hunks): abort safely (git rebase --abort if mid-rebase), write handoff file with notes, print exit report with OUTCOME: blocked and a prose reason above the report block, then EXIT — do NOT force-push a partial resolution

Stay within Safety Rules and the single-commit/push discipline where possible (one rebase resolution = one commit after rebase completes).

Resolving helper scripts (do this first)

You may be spawned against any repo, and most repos carry no .claude/ directory. Never invoke a bare .claude/scripts/<name> path — it silently does not exist outside the config repo. Define these once, then call every helper through run_script:

resolve_script() {
  local name="$1" candidate
  for candidate in \
    "$HOME/.claude/skills-worktree/.claude/scripts/$name" \
    "$HOME/.claude/scripts/$name" \
    ".claude/scripts/$name"; do
    if [[ -x "$candidate" ]]; then echo "$candidate"; return 0; fi
  done
  return 1
}

run_script() {            # run_script <name> [args...]
  local name="$1"; shift
  local path
  if ! path=$(resolve_script "$name"); then
    echo "ERROR: $name not found (checked ~/.claude/skills-worktree/.claude/scripts/, ~/.claude/scripts/, .claude/scripts/)" >&2
    return 127
  fi
  "$path" "$@"
}

Read the full file on GitHub · 266 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. 2d ago First seen · 266 lines · 42 tokens per session scan B b4d85a0996b1

Subscribe to this mod's changes

phase-a-fixer is an agent published in the GitHub repository auerbachb/claude-code-config (5 stars, last pushed 3d ago), licensed MIT. It adds 42 tokens to every session and 3,865 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other agents, from other repositories

quality-engineer

Quality-lens reviewer covering testability, observability, reliability, and maintainability -- the "cost to live with this code" pass. Also drafts contract or construction tests on request. Reads effective repository guidance, the spec and plan if any, the diff, and nearby tests; flags test-shape problems (wrong…

eugenelim/agent-ready-repo · 170 tokens

adversarial-reviewer

Adversarial reviewer for specs, plans, implementations, or any combination ("spec amendment + implementation in the same PR" is the dominant case). Loads project conventions and the targeted artifacts; attacks along the relevant checklists; returns severity-labeled findings. Use after gates pass but before declaring…

eugenelim/agent-ready-repo · 97 tokens

skill-editor

Applies a single, minimal, generalized edit to a Logic-Lens skill (SKILL.md / guide / shared file) given a concrete failure diagnosis. Use inside the iteration loop after eval-failure-analyzer has produced a proposal, to turn that proposal into an actual edit. Mutates files; does NOT run evals or sync the cache — it…

hyhmrright/logic-lens · 84 tokens

bugs-and-security

Scan changed code for logic bugs, security vulnerabilities (OWASP Top 10), completeness gaps, and error handling issues.

ncoevoet/claude-review-all · 28 tokens

security-deep-dive

Conditional threat-model analysis with adversarial reasoning, attack scenarios, and CWE classification. Distinct from agent 02 (which does broad pattern scanning).

ncoevoet/claude-review-all · 35 tokens

api-contract

Detect breaking changes to public APIs, exported types, schemas, REST routes, and DB migrations. Flags consumer-impacting changes that need coordination.

ncoevoet/claude-review-all · 31 tokens