Engineering
Fix a red CI run
Mention Merlin on a pull request with a failing check. It reads the job log, reproduces the failure and pushes a fix, or shows why the test is flaky.
@Merlin when someone asks you about a failing check on a pull request, read the failed job's log with gh, reproduce the failure and push the smallest fix to the same branch. If the test passes on a rerun and the log points to timing or shared state, don't change code: reply with the evidence and call it flaky.
- Starts whenSomeone mentions
@usemerlin-aion a pull request whose checks failed Merlin worksClaude Code or Codex pulls the failed job log with gh, reproduces it and tells a real break from a flaky test
- You getA fix pushed to the branch, or a flake verdict with the evidence, in the pull request
Tools
- GitHub
Capabilities
- Integrations
- Skills
How it works
From red check to green branch.
Mention
@usemerlin-aiunder the failing check and say what you want: a fix, or only the cause.Claude Code or Codex pulls the job log with
gh, runs the failing test on a teammate's machine and tells a real break from a flaky one.A fix lands on the branch with a reply, or Merlin explains why the failure is flaky and leaves the code alone.
Mention @usemerlin-ai under the failing check and say what you want: a fix, or only the cause.
Claude Code or Codex pulls the job log with gh, runs the failing test on a teammate's machine and tells a real break from a flaky one.
A fix lands on the branch with a reply, or Merlin explains why the failure is flaky and leaves the code alone.
acme/web
Type/to searchLMove the session cache to Redis#497Code
Openleewants to merge 4 commits intomainfromlee/session-cache
Some checks were not successful
test / integration (node 22)Failing after 3m
Before and after
Red checks stop waiting for someone to dig in.
Without Merlin
Someone has to stop their own work, open the logs and work out whether the failure is even real.
- 01Open the failed check
- 02Scroll the job log
- 03Find the failing test
- 04Pull the branch
- 05Rerun the test locally
- 06Read the test and the code
- 07Ask who changed the cache
- 08Fix the key prefix
- 09Run the suite again
- 10Push the fix
With Merlin
One mention gets the cause found and the fix pushed while the author keeps working.
@usemerlin-aiunder the failing checkAsked by the author on GitHubReproduces the failure on Lee's MacBookClaude Code with the job log from gh
- Fix pushed, checks run againOr a flake verdict with the evidence
Setup
Install the GitHub app, sign in to gh and hand off red checks.
Set these up once and anyone can hand a failing check to Merlin from the pull request.
- 01Connect a machineRuntimeInstall the Merlin desktop app or CLI on a computer running Claude Code or Codex. You can also use a machine a teammate shares with your workspace.
- 02Install the GitHub appIntegrationsPick the repositories Merlin can access. It sees mentions, reads the pull request and replies in the thread. Pushes use the machine owner's own Git access.
- 03Sign in to the gh CLIRuntimeSome steps use
gh, so sign it in on the machine that runs this. - 04Write down your flaky-test rulesSkills
Keep how your team handles flaky tests in a shared skill, so Merlin knows when to fix and when to report.
- 05Paste the setup promptGuidanceAn owner or admin sends the prompt below to @Merlin once, and it becomes workspace guidance for every future run.
Prompt
Tell Merlin how to handle red checks once.
@Merlin when someone asks you about a failing check on a pull request, read the failed job's log with gh, reproduce the failure and push the smallest fix to the same branch. If the test passes on a rerun and the log points to timing or shared state, don't change code: reply with the evidence and call it flaky.
Once, when you paste it
- PromptYou paste the prompt to @Merlin
- GuidanceMerlin saves your rules as workspace guidance
Every time someone mentions Merlin on GitHub
- IntegrationThe GitHub app spots the mention
- RuntimeMerlin picks an available machine
- ContextThe run gathers context
- WorkClaude Code or Codex reproduces the failure
- SteeringYour team steers the work in the thread
- ResultMerlin pushes a fix or reports a flake
Related use cases
More engineering tasks you can hand to Merlin.
- AutomationsIntegrations
Engineering
Fix the flakiest test every week
Every week, Merlin finds the test that failed most often without a code change, fixes the cause and opens a pull request. You get the link in #eng.
Every Monday at
10:00A fix pull request, linked in#eng - IntegrationsSkillsMemory
Engineering
Address pull request feedback
Mention Merlin on a pull request and get the requested change pushed to your branch. Teammates can steer it in the comments.
@usemerlin-aiin a pull request commentCommits and a reply on the pull request - Integrations
Engineering
Rebase a pull request and fix the conflicts
Mention Merlin on a pull request that conflicts with main. It rebases the branch, resolves the conflicts, runs the tests and pushes.
@usemerlin-aion a pull request with conflictsA rebased branch and a note on each conflict
Bring your coding agents into the tools your team already uses.
Let your whole team hand work to Claude Code and Codex today. Connect one machine and add Merlin to Slack, Linear or GitHub. 14-day free trial, no API keys, no card.