Finish GitHub pull requests by updating branches, monitoring CI, and squash-merging.
npx skills add https://github.com/tkersey/dotfiles --skill fin
Please help me install this Agent Skill. Skill: fin Source: https://github.com/tkersey/dotfiles/tree/main/codex/skills/fin Command: npx skills add https://github.com/tkersey/dotfiles --skill fin
This Skill automates finishing GitHub pull requests end-to-end by updating branches, monitoring CI until checks pass, performing a squash-merge, and cleaning up local and remote state.
Identify the target PR on the current repository and run the finish flow to update the branch, monitor CI until green, squash-merge, and clean up local/remote state.
High-intent search queries and answers about installing and using this skill.
Automating GitHub pull request merging is done by updating the branch, monitoring CI until checks pass, performing a squash-merge, and cleaning up local and remote state automatically. It enforces repo policies for required checks and approvals before merging.
Squash and merge a GitHub PR by running an automated finish flow that updates the branch, waits for CI to pass, applies the squash-merge, and tidies local and remote branch history. This ensures a clean main branch without manual git cleanup.
Monitoring GitHub CI checks before merging a pull request involves watching required checks until they pass green. The automated PR lifecycle enforces repo policies, ensuring required checks and approvals are satisfied before allowing the squash-merge to proceed.
Yes, this PR lifecycle automation relies on standard tooling using gh pr commands and git to perform branch updates, CI monitoring, squash-merging, and state cleanup. It operates within standard GitHub repository environments to enforce checks and approvals.
Yes, you can enforce required approvals on a GitHub pull request before merging. The automation checks that required checks and repo approval policies are satisfied, ensuring the PR is fully validated before the squash-merge and branch cleanup execute.
After a GitHub PR is merged, local and remote branches are cleaned up automatically to tidy history. The finish flow removes obsolete branches across local and remote state, ensuring the repository remains clean following the squash-merge completion.
prismaPrepare and submit external pull requests for the Prisma Next repository.
haleyrcSquash merge feature branch commits into main with a Conventional Commit message.
carterwayneskhizeineAutomate GitHub repository lifecycle tasks via gh or Git/curl APIs.
OmniNode-aiOrchestrate cross-repository pull request merging into GitHub's Merge Queue.
