pr-green-loop

Iterate CI checks, fixes, and re-pushes until GitHub PR checks pass.

5|3|Updated Jun 18, 2024

Search Tags:#automation #github #pr #ci #pull-request #bugbot

Ready to run

npx skills add https://github.com/Unique-AG/ai --skill pr-green-loop

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-green-loop
Source: https://github.com/Unique-AG/ai/tree/main/.claude/skills/pr-green-loop
Command: npx skills add https://github.com/Unique-AG/ai --skill pr-green-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates driving a pull request to green by iterating checks, fixes, and re-pushes until all CI checks pass.

Core Features & Use Cases

Push → wait for CI checks to complete
Fix failures and address Bugbot findings
Re-push in a loop until the PR is green

Quick Start

Push your branch to open or update a PR and let the loop drive CI to green.

Frequently Asked Questions about pr-green-loop

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

FAQPage Schema

How do I automatically fix failing CI checks on a GitHub pull request?▼

You can automatically fix failing CI checks on a GitHub pull request by running an iterative loop that pushes your branch, waits for checks to complete, diagnoses failures, applies fixes, and re-pushes until the PR is green.

Do I need the gh CLI installed to automate PR CI fixes?▼

Yes, you need the gh CLI installed and authenticated to automate PR CI fixes. This workflow requires a remote-tracking GitHub pull request and relies on the gh CLI to interact with checks and push updates.

How does the automated CI remediation loop handle Bugbot findings?▼

The automated CI remediation loop handles Bugbot findings by incorporating them into the iteration cycle. It diagnoses both CI check failures and Bugbot findings, applies necessary remediation, and re-pushes the branch to verify all issues are resolved.

What's the best way to iterate CI fixes and re-pushes until a PR turns green?▼

The best way to iterate CI fixes and re-pushes until a PR turns green is to delegate the diagnosis and fix application to specialized skills. This loop repeatedly pushes updates, waits for CI completion, and applies fixes until all checks pass.

Can I use this approach to remediate Bugbot findings and CI failures across multiple iterations?▼

Yes, you can remediate Bugbot findings and CI failures across multiple iterations. The loop repeatedly checks the pull request status, applies fixes for both CI failures and Bugbot findings, and re-pushes until the PR successfully turns green.

Why does my automated pull request loop require a remote-tracking PR?▼

Your automated pull request loop requires a remote-tracking PR because it needs to monitor and interact with existing GitHub CI checks. Without a remote-tracking PR, the iterative loop cannot wait for checks to complete or push updates to drive the CI status to green.