build-fix

A command that detects the project's build systems, reads build errors, and repeatedly applies fixes until the builds are clean.

In plain words
What is it for?
Use it to fix errors from the detected project builds or from a supplied log file, then recheck all known build systems.
Why use it?
It removes the need to identify each build tool and trace every compiler error by hand, including projects with separate backend and frontend builds.

Command

Part of the go-dev plugin — 3 skills, 10 commands shipped together

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/gopherguides/gopher-ai/build-fix
Clone the repo
git clone --depth 1 https://github.com/gopherguides/gopher-ai

Or install go-dev, the plugin that ships this one along with the rest of its 3 skills, 10 commands.

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,918 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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.01918
Opus 5 $0.00006 $0.00959
Sonnet 5 $0.00003 $0.00384
Haiku 4.5 $0.00001 $0.00192

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

Security

Grade A, and why

build-fix 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 3d 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/go-dev/commands/build-fix.md · 242 lines

How it starts

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

Usage: /build-fix [log-path]

Examples:

  • /build-fix - Auto-detect build system and fix errors
  • /build-fix ./tmp/air-combined.log - Fix errors from a specific log file
  • /build-fix ./build/output.log - Fix errors from custom log location

Loop Initialization

Initialize persistent loop to ensure all build errors are resolved: !if [ ! -x "${CLAUDE_PLUGIN_ROOT}/scripts/setup-loop.sh" ]; then echo "ERROR: Plugin cache stale. Run /gopher-ai-refresh (or refresh-plugins.sh) and restart Claude Code."; exit 1; else "${CLAUDE_PLUGIN_ROOT}/scripts/setup-loop.sh" "build-fix" "COMPLETE"; fi

Step 1: Detect Build Systems

Important: A project may have multiple build systems (e.g., Go backend + Vite frontend). Check ALL of the following independently and collect every detected system. Do not stop after the first match.

If $ARGUMENTS is a file path that exists, use it as an additional log source for error parsing. Still run detection below so all build systems are known for re-checking in Step 6.

Check each build system:

1a. Air (Go hot-reload)

Look for the Air config file:

if [ -f .air.toml ]; then
  AIR_CONFIG=".air.toml"
elif [ -f air.toml ]; then
  AIR_CONFIG="air.toml"
fi

If found, extract tmp_dir and the build log name:

TMP_DIR=$(awk '/^tmp_dir[[:space:]]*=/ { gsub(/.*=[[:space:]]*"|".*/, ""); print; exit }' "$AIR_CONFIG")
TMP_DIR="${TMP_DIR:-tmp}"

BUILD_LOG=$(awk '/^\[build\]/,/^\[/ { if ($0 ~ /^[[:space:]]*log[[:space:]]*=/) { gsub(/.*=[[:space:]]*"|".*/, ""); print; exit } }' "$AIR_CONFIG")
BUILD_LOG="${BUILD_LOG:-build-errors.log}"

Log path priority (check in order, use first that exists):

  1. ${TMP_DIR}/air-combined.log -- primary combined log (compilation + template + SQL errors)
  2. ${TMP_DIR}/${BUILD_LOG} -- Air's configured build error log
  3. Fall through to Go standard build if no logs exist

1b. Go (standard)

[ -f go.mod ]

If go.mod exists, Go is a detected build system. Continue checking for Node systems below -- do not stop here.

Read the full file on GitHub · 242 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. 3d ago First seen · 242 lines · 13 tokens per session scan A 9060e1cab729

Subscribe to this mod's changes

build-fix is a command published in the GitHub repository gopherguides/gopher-ai (21 stars, last pushed 3d ago), licensed MIT. It adds 13 tokens to every session and 1,918 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.