opencode-simple: Command for Claude Code

.opencode/commands/build-fix.md

build-fix is a command for Claude Code, OpenCode from zhmxiaowo/opencode-simple. It costs 24 tokens per session (703 once invoked), scanned A, original, MIT.

A command for diagnosing and fixing build and type errors in software projects. Build errors stop a project from compiling or packaging, while type errors indicate that code uses values inconsistently.

In plain words
What is it for?
It is for running checks in projects using tools such as npm, TypeScript, Rust, Java, Kotlin, Go, Python, .NET, CMake, or Unreal Engine, then fixing errors in dependency order.
Why use it?
It replaces guesswork with an incremental process that identifies the build system, groups errors, and checks each fix.

Command for Claude CodeOpenCode

Written for OpenCode and Claude Code: installed under .opencode/, but also a Claude Code command (commands/*.md). Also seen: agent in frontmatter.

This is zhmxiaowo/opencode-simple's own configuration. It tells Claude Code and OpenCode how to work on opencode-simple itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything opencode-simple configures →

Reuse

Borrowing it

Nothing to install: this file belongs to zhmxiaowo/opencode-simple. 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/zhmxiaowo/opencode-simple/main/.opencode/commands/build-fix.md
Clone the repo
git clone --depth 1 https://github.com/zhmxiaowo/opencode-simple

Made for: Claude Code, OpenCode.

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 build-fix

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/zhmxiaowo/opencode-simple/build-fix"><img src="https://agentmods.dev/badge/commands/zhmxiaowo/opencode-simple/build-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 703 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.00024 $0.00703
Opus 5.5 $0.00010 $0.00281
Sonnet 5.5 $0.00005 $0.00141
Haiku 4.5 $0.00002 $0.00070

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

.opencode/commands/build-fix.md · 73 lines

How it starts

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

Build and Fix (CDD Mode)

Incrementally fix build and type errors with minimal, safe changes. CDD 原则:编译失败时必须调用 sequential-thinking 分析,禁止盲目试错。

Step 1: Detect Build System

Identify the project's build tool and run the build:

Indicator Build Command
package.json with build script npm run build or pnpm build
tsconfig.json (TypeScript only) npx tsc --noEmit
Cargo.toml cargo check 2>&1
pom.xml mvn compile
build.gradle ./gradlew compileKotlin
go.mod go build ./...
pyproject.toml pyright . or mypy .
*.csproj / *.sln dotnet build --no-restore
CMakeLists.txt cmake --build build/
*.uproject UnrealBuildTool

Step 2: Parse and Group Errors

  1. Run the build command and capture stderr
  2. Group errors by file path
  3. Sort by dependency order (fix imports/types before logic errors)
  4. Count total errors for progress tracking

Step 3: Fix Loop (CDD Mode — Think Before Fix)

For each error:

  1. Read the file — Use Read tool to see error context (10 lines around the error)
  2. Think first — Invoke sequential-thinking MCP to analyze root cause (禁止盲目试错)
  3. Diagnose — Identify root cause (missing import, wrong type, syntax error)
  4. Fix minimally — Use Edit tool for the smallest change that resolves the error
  5. Re-run build — Verify the error is gone and no new errors introduced
  6. Move to next — Continue with remaining errors

Step 4: Guardrails

Stop and ask the user if:

  • A fix introduces more errors than it resolves
  • The same error persists after 3 attempts (likely a deeper issue)
  • The fix requires architectural changes (not just a build fix)
  • Build errors stem from missing dependencies (need npm install, cargo add, etc.)

Step 5: Summary

Show results:

  • Errors fixed (with file paths)
  • Errors remaining (if any)
  • New errors introduced (should be zero)
  • Suggested next steps for unresolved issues

Read the full file on GitHub · 73 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 · 73 lines · 24 tokens per session scan A 1c683d0c6b44

Subscribe to this mod's changes

build-fix is a command published in the GitHub repository zhmxiaowo/opencode-simple (2 stars, last pushed 7mo ago), licensed MIT. It adds 24 tokens to every session and 703 once invoked, about $0.0001 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.

Related

Other commands, from other repositories