join_skill

This skill automates PR orchestration using gh commands to keep PRs green and ready for human handoff.

Python

42

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill tkersey/dotfiles --skill join

SKILL.md10.0 KB

Overview

This skill runs a PR autopilot that uses the GitHub CLI (gh) only to create, manage, and keep pull requests merge-ready without merging them. It enforces required CI gates, applies minimal surgical fixes via the GitHub API, and publishes a clear human handoff when PRs are green. The operator respects hold signals and never approves or merges PRs unless explicitly instructed.

How this skill works

The operator runs a monitor loop that discovers branches, creates PRs where missing, and processes open PRs sequentially using gh commands only. For each PR it enforces required checks, watches CI progress, attempts small automated fixes through gh api when safe, and updates a single status comment named "Join Operator." If an action cannot be completed within the gh-only boundary, it applies auto:hold and leaves a blocking comment.

When to use it

Automate creation of PRs for branches discoverable via GitHub API.
Keep branches current and required CI checks passing without local checkouts.
Apply minimal, API-only fixes for CI failures on behalf of contributors.
Prepare PRs to be merge-ready and publish a clear handoff for humans to merge.
Monitor PRs continuously and pause automation using labels when needed.

Best practices

Ensure gh is authenticated (gh auth status) before starting the operator.
Require labels auto:manage (opt-in) and auto:hold (pause automation) in the repo.
Run in gh-only remote mode—do not assume local workspace or run git commands.
Limit surgical fix attempts (default 3) and fallback to auto:hold with a summary comment on failure.
Maintain a single in-place comment/check-run named Join Operator to avoid comment spam.

Example use cases

Repo maintainer wants automated PR creation for non-default branches and CI enforcement using only gh commands.
Contributor adds auto:manage label to opt into automated branch upkeep and fixes for failing checks.
Operator detects required checks stalled, applies auto:hold, and leaves a diagnostic comment linking stuck runs.
Small CI failure (typo, config tweak) is corrected via gh api edit to the head branch and checks are re-run until green.
Prepare many contributors' PRs to a handoff state so maintainers can review and merge locally when ready.

FAQ

No. It never runs gh pr merge or gh pr review --approve unless you explicitly instruct it to do so.

What happens for CI failures that require local edits or complex merges?

It applies auto:hold and leaves a blocking comment using the gh-only block template, guiding a human to perform the required local action and remove auto:hold afterward.