ENGINEERING

Open an auto-skip pull request for confirmed flaky specs

When a spec crosses the confirmed-flake threshold, an agent edits the test file to add a skip annotation with a quarantine reference, opens a draft pull request.

CategoryEngineering
Enginepaperclip
Difficultyadvanced
Triggerwebhook
Steps4
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWebhook: spec confirmed flakyHTTP webhook
  • ActionLocate spec and edit skip annotationGitHubGitHub
  • LogicVerify single-spec minimal diff
  • OutputOpen draft PR linked to quarantine issueGitHubGitHub

What it does

Closes the loop between detection and unblocking CI. Rather than asking a human to manually disable a known-flaky test, it produces a reviewable draft PR that adds a skip/quarantine annotation pointing back to the tracking issue, so merges stop failing while the fix is still tracked.

When to use it

Use this once a spec is confirmed flaky (not a real regression) and is repeatedly blocking unrelated PRs. The draft-PR approach keeps a human in the loop for the actual merge.

How it works

  1. 1A webhook fires when a spec is confirmed flaky and has an open quarantine issue.
  2. 2An agent locates the test file and the exact spec via the GitHub API.
  3. 3It edits the file to add the framework's skip/quarantine annotation with a comment linking the issue number.
  4. 4A logic check confirms exactly one spec was modified and the diff is minimal before proceeding.
  5. 5The flow opens a draft pull request referencing the tracking issue and requests review from the owning team.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect GitHubRepos, issues, pull requests, actions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.