pr-workflow-automation

Automate GitHub pull requests with git and gh, monitoring CI and retrying failures.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/shepherdjerred/dotfiles --skill pr-workflow-automation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-workflow-automation
Source: https://github.com/shepherdjerred/dotfiles/tree/main/private_dot_claude/skills/pr-workflow-automation
Command: npx skills add https://github.com/shepherdjerred/dotfiles --skill pr-workflow-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the complete pull request workflow, eliminating manual steps to push changes, create PRs, and monitor CI status, including automatic amendments and retries when checks fail.

Core Features & Use Cases

  • Automates pushing changes and creating PRs with GitHub CLI.
  • Monitors CI status and PR checks, alerting on completion or failures.
  • Automatically handles CI failures by amending commits, force-pushing, and retrying until CI passes.
  • Suitable for branch-based collaboration across teams and when CI-driven PR management is required.

Quick Start

Push the current branch to the remote, create a PR, and monitor CI until green. For example:

  • git push -u origin $(git branch --show-current)
  • gh pr create --fill
  • gh pr checks --watch
  • If CI fails, amend the commit and push with --force-with-lease

Frequently Asked Questions about pr-workflow-automation

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

FAQPage Schema
How do I automate GitHub pull request workflows and monitor CI status?▼

Automating GitHub pull request workflows involves pushing changes, creating PRs via the gh CLI, and polling CI checks. When checks fail, the process automatically amends commits and force-pushes with retries until CI passes.

Can I automatically retry failed CI checks by amending commits in git?▼

You can automatically retry failed CI checks by amending the git commit and force-pushing with --force-with-lease. This workflow uses a configurable max_retries limit and polling interval to monitor and fix failures until CI passes.

What is needed to set up CI-aware PR management for branch-based team collaboration?▼

CI-aware PR management requires standard git and gh tooling to push changes and create pull requests. It targets GitHub-based development workflows, enabling teams to automatically monitor status and handle failures across branches.

Does this PR automation work with standard git and GitHub CLI tooling?▼

Yes, this PR automation relies entirely on standard git and GitHub CLI tooling. It executes deterministic steps like git push, gh pr create, and gh pr checks to manage pull requests without requiring external dependencies.

What are the limitations of using force-push to amend commits during CI retries?▼

Using force-push to amend commits during CI retries is limited to branches where history rewrites are safe. It uses --force-with-lease to prevent overwriting remote changes, but may disrupt branch-based collaboration if others have pulled the original commits.