skills.rest
tigredonorte
tigredonorteCOMMUNITY
Explore all skills by this author →
GitHub

follow-up-pr

Monitor PR CI status and apply automated fixes until checks pass.

Updated Feb 25, 2026
Search Tags:#automation#github#pr#diagnose#retry#ci
One-click install
npx skills add https://github.com/tigredonorte/claude-plugin-work --skill follow-up-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: follow-up-pr
Source: https://github.com/tigredonorte/claude-plugin-work/tree/main/skills/follow-up-pr
Command: npx skills add https://github.com/tigredonorte/claude-plugin-work --skill follow-up-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monitoring and stabilizing PR CI across workflows, automatically diagnosing failures and applying fixes to drive a PR to a passing CI.

Core Features & Use Cases

  • CI status surveillance for the current PR and automated retry loops
  • Automated conflict resolution prompts and diagnostics with GitHub CLI
  • End-to-end workflow orchestration across checks, fixes, and re-checks in feature branches
  • Fits into multi-branch development pipelines with reusable decision rules

Quick Start

Run the /follow-up-pr command to start monitoring the current PR's CI and auto-fix failures until it passes.

Frequently Asked Questions about follow-up-pr

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

FAQPage Schema
How do I automate GitHub PR CI monitoring and auto-fix retries?▼

Automate PR CI monitoring by running a command that checks the current pull request status, diagnoses failures, applies automated fixes, and retries until CI passes across multiple attempts.

How does automated conflict resolution work during CI retries?▼

Automated conflict resolution uses GitHub CLI to detect failing PR checks, prompt diagnostics, and apply fixes automatically within the retry loop to stabilize the CI pipeline.

Can I use this to monitor CI status across multiple feature branches?▼

Yes, the automated retry logic fits into multi-branch development pipelines, monitoring CI status and applying reusable decision rules across feature branches within your software development workflow.

Do I need GitHub CLI to run automated PR diagnostics and retries?▼

Yes, GitHub CLI is required to query PR checks, run diagnostic checks, and apply automated fixes during the retry loop until the CI status passes.

What is the best way to keep a failing pull request CI passing automatically?▼

The best way is to use an automated workflow that monitors the current PR CI status, applies configurable retry logic, and runs diagnostic fixes until all checks pass.

Why does my PR CI keep failing after automated fixes?▼

PR CI may still fail if the configurable retry attempts are exhausted or if conflict resolution prompts require manual intervention that the automated GitHub CLI diagnostics cannot resolve.

Related Skills

Explore More Software Engineering Skills→
StudyDriftStudyDrift
58

loop-on-ci

Monitor GitHub PR CI checks and re-run them until all pass.

Official
Intermediate
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

staging-deployment-phase

Coordinate staging deployments with migrations, health checks, and verification.

Community
Intermediate
amo-tech-aiamo-tech-ai

cicd-pipeline

Automate GitHub Actions CI/CD pipelines for build, test, lint, and deployment workflows.

Community
Intermediate
oysteinkrogoysteinkrog

fix-pr

Monitor and repair GitHub PR checks until all CI checks pass.

Community
Advanced