skills.rest
samjonester
samjonesterCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr-ci-autofix

Monitor PR CI status and triage failures across GitHub and Buildkite.

5|1|Updated Nov 4, 2015
Search Tags:#automation#github#pr#buildkite#triage#ci
One-click install
npx skills add https://github.com/samjonester/dotfiles --skill pr-ci-autofix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-ci-autofix
Source: https://github.com/samjonester/dotfiles/tree/main/personal/pi/skills/pr-ci-autofix
Command: npx skills add https://github.com/samjonester/dotfiles --skill pr-ci-autofix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates continuous PR CI monitoring and automatic triage/fix workflows in response to CI results.

Core Features & Use Cases

  • Continuous PR CI monitoring and automatic triage/fix workflows.
  • Resolve PR metadata, fetch status, identify root causes, and propose fixes.
  • Use case: when a PR's CI is flaky or failing, this skill will triage and suggest fixes and re-run CI after user confirmation.

Quick Start

Start monitoring a PR's CI status and automatically triage failures, prompting you to approve retriggers before re-running CI.

Frequently Asked Questions about pr-ci-autofix

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

FAQPage Schema
How do I automatically triage failing PR CI builds?▼

You can automatically triage failing PR CI builds by providing a PR URL or number to this skill, which then identifies the root cause and proposes fixes. It operates across GitHub PRs and Buildkite pipelines to monitor status and iterate fixes.

Can I monitor Buildkite pipeline status from a GitHub PR?▼

Yes, you can monitor Buildkite pipeline status directly from a GitHub PR. The skill fetches status using the gh CLI and Buildkite tools, resolving PR metadata to identify failures across both platforms.

How does automatic CI retriggering work after fixing a PR?▼

Automatic CI retriggering works by leveraging the gt modify and gt submit workflow to apply approved changes, then using a Cron-based loop to re-run CI. It prompts you to approve retriggers before executing the CI re-run.

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

Yes, you need the gh CLI to automate PR CI monitoring because the skill uses gh pr view outputs to fetch status and resolve metadata. It relies on gh CLI alongside Buildkite tools to operate across platforms.

What is the best way to continuously monitor flaky CI on a pull request?▼

The best way to continuously monitor flaky CI on a pull request is using a Cron-based loop that checks status and automatically triages failures. This skill resolves PR metadata, identifies root causes, and suggests fixes for flaky or failing pipelines.

Why does my PR CI triage require manual approval before retriggering?▼

Your PR CI triage requires manual approval before retriggering to ensure proposed fixes are reviewed before re-running CI. The skill suggests fixes and prompts you to approve retriggers, preventing unverified changes from automatically executing.

Related Skills

Explore More Software Engineering Skills→
theZMCtheZMC
2

read-github-issue

Read GitHub issue status, metadata, and comments via gh CLI.

Community
Intermediate
nthpaulnthpaul

pr-stack-ship

Restack and submit Graphite pull request stacks after local commits.

Community
Intermediate
NachoFLizaurNachoFLizaur
3

corvus-review-r0

Parse PR references, fetch metadata via gh pr view, and produce PR_CONTEXT.

Community
Advanced
technicalpicklestechnicalpickles
10

working-with-buildkite-builds

Fetch and interpret Buildkite build data to diagnose failures and reproduce issues locally.

Community
Advanced