join

Automate GitHub PR management with CI gates and squash-merge via gh CLI.

66|2|Updated Feb 18, 2015

Search Tags:#workflow #GitHub #merge #PR automation #gh CLI #CI gates

Ready to run

npx skills add https://github.com/tkersey/dotfiles --skill join

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: join
Source: https://github.com/tkersey/dotfiles/tree/main/codex/skills/join
Command: npx skills add https://github.com/tkersey/dotfiles --skill join

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill automates GitHub PR management, including PR creation and updates, CI gate enforcement, automated fixes, and squash-merge through the gh CLI to keep PRs healthy with minimal manual intervention.

Core Features & Use Cases

Continuous PR operator: keep PRs healthy, green, reviewed, and ready for merge across multiple repositories.
Enforce CI gates and surgical fixes: ensure required checks pass and apply minimal, targeted changes to fix CI failures.
Post-merge workflow: perform cleanup and maintain a clean repository state after merges.
Per-PR modes: operate in local (checked-out branch) or remote-only modes depending on the workspace state.

Quick Start

Ensure gh auth status succeeds.
Ensure labels exist: auto:manage, auto:hold.
(Optional) Add .github/auto-merge.yml from assets/auto-merge.yml.
Start the monitor loop.

Frequently Asked Questions about join

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

FAQPage Schema

How do I automate GitHub PR merges with CI gates using the gh CLI?▼

You can automate GitHub PR merges with CI gates by running a continuous operator loop that enforces required checks, applies surgical fixes, and performs squash-merges via the gh CLI. This keeps PRs healthy with minimal manual intervention across multiple repositories.

What is the best way to enforce CI gates and apply automated fixes to failing pull requests?▼

The best way to enforce CI gates is to use an automated PR manager that monitors open PRs, verifies required checks pass, and applies minimal targeted changes to resolve failures. This ensures consistent CI gating and maintains repository hygiene.

Can I manage multiple repository PRs and maintain post-merge cleanup automatically?▼

Yes, you can manage multiple repository PRs and perform post-merge cleanup automatically using a centralized operator. It processes open PRs, applies CI gates, and maintains a clean repository state after merges are completed.

Do I need specific labels and authentication configured before starting PR automation?▼

Yes, you need gh auth status to succeed and specific labels like auto:manage and auto:hold to exist before starting. You can optionally add .github/auto-merge.yml from the provided assets to configure the automated merge workflow.

Does this PR automation workflow support both local checked-out branches and remote-only modes?▼

Yes, this PR automation workflow supports per-PR modes for both local checked-out branches and remote-only operations. This flexibility allows it to adapt to different workspace states when processing pull requests.