make-ci-green

Re-runs failed Chelimba CI jobs for a specified pull request number in the brave/brave-core repository.

4|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/brave-experiments/brave-core-bot --skill make-ci-green
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make-ci-green
Source: https://github.com/brave-experiments/brave-core-bot/tree/main/.claude/skills/make-ci-green
Command: npx skills add https://github.com/brave-experiments/brave-core-bot --skill make-ci-green

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automatically re-runs failed CI jobs for pull requests, saving developers time and ensuring faster integration of code changes.

Core Features & Use Cases

  • Automated Retries: Detects failing Jenkins CI checks and triggers a re-run.
  • Smart Failure Detection: Differentiates between build/infrastructure failures (requiring a workspace wipe) and test/storybook failures (requiring a normal re-run).
  • Test Failure Analysis: For test failures, it analyzes the root cause, checks for upstream flakiness, assesses PR correlation, and suggests filing new issues if necessary.
  • Use Case: A developer pushes a change, and the CI build fails due to a flaky test. They can use this Skill to automatically re-run the CI, potentially fixing the build without manual intervention.

Quick Start

Use the make-ci-green skill to re-run CI for pull request number 33936.

Frequently Asked Questions about make-ci-green

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically re-run failed Jenkins CI jobs for a pull request?

You can automatically re-run failed Jenkins CI jobs by targeting a specific pull request number, which triggers a re-run based on the detected failure stage. This automates the retry process without manual intervention.

How does automated CI failure detection differentiate between infrastructure and test failures?

Automated CI failure detection differentiates by applying a workspace wipe for build or infrastructure issues, while triggering a normal re-run for test or storybook failures. This ensures the correct retry strategy is used.

Can I analyze test failure root causes and check for upstream flakiness in Jenkins?

Yes, you can analyze test failure root causes and check for upstream flakiness during the CI re-run process. The system assesses PR correlation and suggests filing new issues when appropriate to track flaky tests.

What is the best way to fix broken CI builds caused by flaky tests in a pull request?

The best way to fix broken CI builds caused by flaky tests is to automatically detect the failing stage and trigger a normal re-run. This analyzes the failure and potentially fixes the build without manual debugging.

When should I use a workspace wipe to fix a failing Jenkins CI build?

You should use a workspace wipe to fix a failing Jenkins CI build when the failure is related to build or infrastructure issues. This clears corrupted state, whereas test failures only require a normal re-run.

Does this automated CI re-run process work with the brave-core repository?

Yes, the automated CI re-run process works specifically with the brave/brave-core repository to re-run failed Jenkins CI jobs. It requires a specified pull request number to identify and process the correct build.