Merge GitHub pull requests with squash after CI checks pass.
npx skills add https://github.com/proven-xyz/proven-app --skill pr-merge-proven-xyz
Please help me install this Agent Skill. Skill: pr-merge Source: https://github.com/proven-xyz/proven-app/tree/main/.agents/skills/pr-merge Command: npx skills add https://github.com/proven-xyz/proven-app --skill pr-merge-proven-xyz
Merge GitHub pull requests with strict CI validation. Never bypasses failed checks. Use when merging PRs or when user says /pr-merge.
Use the pr-merge skill to merge a PR only after all checks pass or when the user explicitly requests /pr-merge.
High-intent search queries and answers about installing and using this skill.
Automating a GitHub pull request merge with strict CI validation requires enforcing checks before executing a squash merge. This process prevents bypassing failed validation and ensures code stability by using the GitHub CLI to merge only when all status checks succeed.
Merging a pull request via the command line without bypassing failed CI checks requires a strict validation mechanism. By using the GitHub CLI to enforce checks, the merge process halts if validation fails, ensuring that only successfully validated code is merged.
Automating pull request merges requires the GitHub CLI installed and authenticated, an existing pull request for the target branch, and proper repository access. These prerequisites ensure the merge process can execute squash merges and validate CI checks successfully.
An automated pull request merge fails when CI checks are not passing because the process strictly enforces validation and prevents bypasses. If checks fail, the system intentionally halts the squash merge to ensure that unvalidated or broken code is never merged into the repository.
You should use an automated CI-validated merge when you need to safely merge pull requests across repositories and guarantee that no failing checks are bypassed. It is applicable whenever you are merging branches or explicitly request a validated squash merge.
The automated PR merge process uses squash merging to integrate pull requests. By executing a squash merge with the GitHub CLI, it combines all commits into one while strictly enforcing CI validation to prevent bypassing any failed checks before the merge completes.
tkerseyFinish GitHub pull requests by updating branches, monitoring CI, and squash-merging.
doravidanMerge RALPH worktree changes into the main branch with optional squash.
johinsDevConfigure validate-only GitHub Actions CI for Next.js monorepo PRs.
adaptive-enforcement-labEnforce required CI status checks on GitHub pull requests before merge.
