Borrowing it
Nothing to install: this file belongs to Piyush8296/claude-workspace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Piyush8296/claude-workspace/main/.claude/commands/build-fix.mdgit clone --depth 1 https://github.com/Piyush8296/claude-workspaceWrote 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.
[](https://agentmods.dev/commands/piyush8296/claude-workspace/build-fix)<a href="https://agentmods.dev/commands/piyush8296/claude-workspace/build-fix"><img src="https://agentmods.dev/badge/commands/piyush8296/claude-workspace/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.
<a href="https://agentmods.dev/commands/piyush8296/claude-workspace/build-fix"><img src="https://agentmods.dev/badge/commands/piyush8296/claude-workspace/build-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00012 | $0.00535 |
| Opus 5 | $0.00006 | $0.00267 |
| Sonnet 5 | $0.00002 | $0.00107 |
| Haiku 4.5 | $0.00001 | $0.00053 |
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 8d 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.
What it actually says
Build Fix
Diagnose and fix build errors: $ARGUMENTS
Instructions
1. Run the build
# Try project's build command
pnpm build 2>&1 || npm run build 2>&1
Capture the full error output.
2. Parse errors
For each error, identify:
- File and line number
- Error type (TypeScript, ESLint, import resolution, runtime)
- Root cause (not just the symptom)
Group errors by type. Fix in this priority order:
- Import/module resolution errors (missing deps, wrong paths)
- TypeScript type errors
- ESLint errors
- Runtime/logic errors
3. Fix iteratively
For each error group:
a. Read the failing file and surrounding context
b. Identify the root cause (not just the error line)
c. Apply the fix
d. Run build again to verify
e. If new errors appear, continue the loop
f. If the same error persists after 3 attempts, STOP and report
Rules:
- Fix root causes, not symptoms
- Never suppress errors with
@ts-ignoreoreslint-disableunless explicitly approved - If a fix introduces new errors, revert and try a different approach
- Maximum 10 fix iterations before stopping
4. Run full verification
After build passes:
# Type check
npx tsc --noEmit
# Lint
npx eslint src/ --no-error-on-unmatched-pattern
# Tests
npx vitest run --reporter=verbose 2>&1 | tail -30
5. Commit if clean
git add -A
git diff --cached --stat
git commit -m "fix: resolve build errors"
6. Report
## Build Fix Summary
**Status**: FIXED / PARTIALLY FIXED / BLOCKED
**Errors found**: X
**Errors fixed**: Y
**Iterations**: Z
### Fixes Applied
- [file:line] — description of fix
### Remaining Issues (if any)
- [file:line] — why this couldn't be auto-fixed
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.
- 8d ago First seen · 92 lines · 12 tokens per session scan A 2a3cb8ae7666
build-fix is a command published in the GitHub repository Piyush8296/claude-workspace (2 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 535 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-31.
Other commands, from other repositories
bootstrap
Verifies and repairs the Claude Code Toolkit installation.
cleanup
You are executing the /dogma:cleanup command. Your task is to find and fix AI-typical patterns in the codebase that reveal AI/agent usage.
lint
You are executing the /dogma:lint command. Your task is to detect the project type and run appropriate linting and formatting tools on staged files before commit.
hades-show-traces
Point the user to Charon, Hades' trace explorer.
backprop
Trace a bug back to a spec gap and generate regression tests.
debug-trace
You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, and establish troubleshooting practices for development and production environments.