Best use case
build-fix is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Diagnose and fix build failures or CI issues
Teams using build-fix should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/build-fix/SKILL.md --create-dirs "https://raw.githubusercontent.com/hivellm/rulebook/main/.claude/skills/build-fix/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/build-fix/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How build-fix Compares
| Feature / Agent | build-fix | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Diagnose and fix build failures or CI issues
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Diagnose and fix the current build failure. If $ARGUMENTS is provided, focus on that specific build error or CI job. Steps: 1. Run the build command and capture the error output 2. Read the error message and trace to the source file 3. Identify the root cause (missing dep, type error, config issue) 4. Apply the minimal fix 5. Re-run the build to verify the fix works
Related Skills
We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.