greenlight-pr

Automates GitHub PR health by triaging CI failures and bot reviews.

47|5|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/zvadaadam/az-skills --skill greenlight-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: greenlight-pr
Source: https://github.com/zvadaadam/az-skills/tree/main/skills/engineering/greenlight-pr
Command: npx skills add https://github.com/zvadaadam/az-skills --skill greenlight-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Greenlight-pr automates the painful, repetitive process of bringing PRs to merge readiness by handling CI failures and triaging AI bot reviews, letting engineers focus on meaningful changes.

Core Features & Use Cases

  • Snapshot PR state (CI, checks, and bot reviews)
  • Triage bot comments and fix or wait
  • Retry flaky CI and post round summaries
  • Wait for bot re-review before proceeding

Quick Start

Run python3 gl-snapshot.py <PR-number-or-URL> to bootstrap Greenlight PR on your target.

Frequently Asked Questions about greenlight-pr

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

FAQPage Schema
How do I automate GitHub PR triage and fix CI failures automatically?

Automating GitHub PR triage involves diagnosing CI failures and bot reviews, applying retries for flaky runs, and orchestrating snapshot, triage, fix, and report steps to drive PRs to merge readiness.

What is the best way to handle flaky CI runs on a pull request?

Handling flaky CI runs requires an automated triage process that orchestrates retries for flaky runs, snapshots PR state, and posts round summaries while maintaining persistent state across multiple attempts.

How do I triage inline bot comments on GitHub pull requests?

Triaging inline bot comments on GitHub pull requests requires snapshotting the PR state, categorizing bot feedback, and applying explicit action flows to either fix issues or wait for bot re-reviews.

Can I automate waiting for a bot re-review before merging a PR?

Yes, you can automate waiting for bot re-reviews by orchestrating round summaries and persistent state, allowing the PR health process to pause and proceed only after bot reviews are resolved.

How do I start automating PR health for a specific GitHub pull request?

To start automating PR health, execute the snapshot script with the target PR number or URL to bootstrap the diagnostic process, capturing CI results, checks, and bot reviews.