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.

acme/web · pull requests
Get started for free
  1. Starts whenSomeone mentions @usemerlin-ai on a pull request whose checks failed
  2. Merlin worksClaude Code or Codex pulls the failed job log with gh, reproduces it and tells a real break from a flaky test
  3. 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-ai under the failing check and say what you want: a fix, or only the cause.

acme/web

Type/to searchL
CodeIssues8Pull requests12AgentsActionsProjectsSecurityInsightsSettings

Move the session cache to Redis#497Code

Openleewants to merge 4 commits intomainfromlee/session-cache

Conversation 5 Commits 4 Checks 3 Files changed 3+48−6

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.

  1. 01Open the failed check
  2. 02Scroll the job log
  3. 03Find the failing test
  4. 04Pull the branch
  5. 05Rerun the test locally
  6. 06Read the test and the code
  7. 07Ask who changed the cache
  8. 08Fix the key prefix
  9. 09Run the suite again
  10. 10Push the fix

With Merlin

One mention gets the cause found and the fix pushed while the author keeps working.

  1. @usemerlin-ai under the failing checkAsked by the author on GitHub
  2. Reproduces the failure on Lee's MacBookClaude Code with the job log from gh
  3. 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.

  1. 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.
  2. 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.
  3. 03Sign in to the gh CLIRuntimeSome steps use gh, so sign it in on the machine that runs this.
  4. 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.

  5. 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.

acme/web · pull requests

Once, when you paste it

  1. PromptYou paste the prompt to @Merlin
  2. GuidanceMerlin saves your rules as workspace guidance

Every time someone mentions Merlin on GitHub

  1. IntegrationThe GitHub app spots the mention
  2. RuntimeMerlin picks an available machine
  3. ContextThe run gathers context
  4. WorkClaude Code or Codex reproduces the failure
  5. SteeringYour team steers the work in the thread
  6. ResultMerlin pushes a fix or reports a flake

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.