mirzaaghazadeh/standbye/fixing-a-red-build
Claude Code and agent skill by mirzaaghazadeh/standbye
- community
Checking that the SKILL.md file is still in the repository.
Handle a broken default branch or failing CI — establish what broke and when, get the branch green the fastest safe way, then fix it properly. Use the moment you notice main is red or the suite fails for reasons that are not yours.
Install
npx vskill@latest install mirzaaghazadeh/standbye/fixing-a-red-buildSKILL.md
The same SKILL.md was published earlier as mirzaaghazadeh/standbye/fixing-a-red-build.
Fixing a red build
A red default branch blocks everyone on the team. It outranks whatever you were doing.
First, be sure
Run the failing check yourself before you announce anything. A CI failure caused by a dead network, an expired token, or a full disk is a different problem with a different owner, and calling it a code break wastes the team's morning.
Say plainly what you observed: the command, the failure, and whether it reproduces locally.
Then find the boundary
Find the last commit where the check passed and the first where it failed. git log on the touched files, or git bisect when the range is wide. Name the commit and the person who made it — not to assign blame, but because they can usually explain it in one line.
Tell the team in the channel they watch, with the failing test name and the suspect commit. One message, with evidence. Do not speculate about the cause in public before you have the boundary.
Get green before you get clever
Two paths, and the choice is about time:
- Revert when the break is not obvious within a few minutes, when the author is not around, or
when the change is large. Reverting is not an insult; it is the cheap, reversible option that unblocks everyone. Then fix it properly on a branch.
- Fix forward when the cause is plain and the fix is small — a missed rename, a wrong import,
a fixture that needs updating.
Either way, the change that makes main green is small, targeted, and reviewed like any other. Do not bundle unrelated cleanup into a hotfix.
Reverting is still a change the owner may need to approve
Your rules probably forbid pushing to the default branch without approval, and an emergency does not repeal them. If you need to push a revert and cannot, use ask_user with a one-line title, the evidence, a recommendation, and a default_answer so it resolves even if the owner is asleep.
Afterwards
- Add the test or check that would have caught it. A break that CI could not see is a gap in CI.
- Call
rememberif the cause was a trap the team will hit again — a step that must run first, a
dependency that is not pinned, a test that depends on the clock.
- If the break came from a habit rather than a mistake, raise it at the retrospective rather than
in the moment.
What not to do
- Do not disable, skip, or delete the failing test to get green. That is not green.
- Do not rewrite shared history to hide the bad commit.
- Do not sit on a red branch quietly because you assume someone else noticed.
Security
- Security scanPassed, 86 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingpackages/supervisor/skills/fixing-a-red-build/SKILL.md
Popularity
- 7-day trend score
- 5
Refreshed 12 Oct 2026, a month ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/mirzaaghazadeh/standbye/fixing-a-red-build)