Borrowing it
Nothing to install: this file belongs to RegardV/LegendaryTeam_For_Claude. 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/RegardV/LegendaryTeam_For_Claude/main/.claude/commands/build-fix.mdgit clone --depth 1 https://github.com/RegardV/LegendaryTeam_For_ClaudeWrote 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/regardv/legendaryteam_for_claude/build-fix)<a href="https://agentmods.dev/commands/regardv/legendaryteam_for_claude/build-fix"><img src="https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/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/regardv/legendaryteam_for_claude/build-fix"><img src="https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/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.00000 | $0.02506 |
| Opus 5 | $0.00000 | $0.01253 |
| Sonnet 5 | $0.00000 | $0.00501 |
| Haiku 4.5 | $0.00000 | $0.00251 |
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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 528 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/build-fix - Build Error Diagnosis & Resolution
Diagnose and fix build errors, compilation failures, and dependency issues.
Usage
# Diagnose and fix build errors
/build-fix
# Fix specific build error
/build-fix "Module not found: Can't resolve 'react'"
# Fix TypeScript errors
/build-fix typescript
# Fix dependency issues
/build-fix deps
# Verbose mode with detailed diagnostics
/build-fix --verbose
What This Command Does
- Runs build to identify errors
- Analyzes error messages and stack traces
- Diagnoses root cause of build failures
- Implements fixes systematically
- Verifies build succeeds after fixes
- Reports what was fixed and why
Command Flow
Step 1: Run build and capture errors
→ npm run build (or equivalent)
→ Collect all error messages
→ Categorize errors by type
Step 2: Analyze errors
→ TypeScript errors
→ Module resolution errors
→ Dependency errors
→ Configuration errors
Step 3: Fix errors systematically
→ Start with blocking errors
→ Fix one category at a time
→ Verify each fix
Step 4: Verify and report
→ Run full build
→ Confirm success
→ Document fixes applied
Invokes Agent
@BugResolver will handle this command with the following context:
Task: Diagnose and fix build errors
Context: Build is currently failing
Requirements:
1. Run build to identify all errors
2. Categorize and prioritize errors
3. Fix errors systematically (one at a time)
4. Verify build succeeds after each fix
5. Document all fixes applied
6. Report root causes and prevention strategies
Output:
- List of errors found
- Fixes applied for each error
- Build status (success/failure)
- Recommendations for prevention
Common Build Errors & Fixes
1. TypeScript Type Errors
Error:
src/auth.ts(45,12): error TS2339: Property 'id' does not exist on type 'User | null'
Diagnosis:
- TypeScript can't guarantee
useris not null - Accessing
user.idwithout null check fails type checking
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.
- 10d ago First seen · 528 lines · 0 tokens per session scan A d5e8bf4ff9f7
build-fix is a command published in the GitHub repository RegardV/LegendaryTeam_For_Claude (19 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,506 tokens. 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.
Other commands, from other repositories
hatch3r-bug-plan
Diagnose a complex incident -- reproduce the symptom, rank root-cause hypotheses, design the fix path, and emit regression coverage items as a board-ready investigation.
api
Debug API and data flow issues by tracing through Component -> TanStack Query -> Express Route -> Service -> SQLite/JSONL.
logs
Analyze server logs to diagnose errors, exceptions, and unexpected behavior.
performance
Diagnose performance issues including slow renders, bundle size, N+1 queries, and memory leaks.
data
Inspect database and state files to debug data issues.
browser
Debug and fix browser issues by inspecting, diagnosing, and resolving visual or technical problems.