skills.rest
gannonh
gannonhCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pull-requests

Automate pull-request creation, review, and merge with gh CLI.

1|Updated Jun 19, 2026
Search Tags:#git#merge#code-review#CI#pull-requests#gh-cli
One-click install
npx skills add https://github.com/gannonh/kata-agents --skill pull-requests-gannonh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pull-requests
Source: https://github.com/gannonh/kata-agents/tree/main/skills/pull-requests
Command: npx skills add https://github.com/gannonh/kata-agents --skill pull-requests-gannonh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the end-to-end pull request workflow, reducing manual steps and context switching by orchestrating PR creation, review, and merge through the gh CLI.

Core Features & Use Cases

  • PR Creation: Create a new PR from a feature branch, including branch setup and push.
  • Code Review & Quality Checks: Trigger or simulate reviews, enforce approvals, and surface issues before merging.
  • PR Merging & Cleanup: Merge PRs after CI checks pass and clean up branches when appropriate.

Quick Start

Use the pull-requests skill to create or review a PR from the current branch and merge when CI passes.

Frequently Asked Questions about pull-requests

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

FAQPage Schema
How do I automate pull request workflows using gh CLI?▼

Automate pull request workflows with gh CLI by orchestrating PR creation, code review, and merging into a deterministic lifecycle. The Skill handles branch setup, pushes, and merges after CI checks pass, reducing manual steps and context switching.

Can I enforce code reviews and approvals before merging a PR?▼

Yes, code reviews and approvals are enforced before merging a PR. The Skill triggers reviews, surfaces issues, and verifies that CI checks pass before executing the merge through gh CLI to maintain standardized governance.

Do I need gh CLI installed and configured to automate PR lifecycles?▼

Yes, gh CLI must be installed and configured against your Git repository to automate PR lifecycles. Familiarity with branch strategies and PR states like open or merged is also assumed for proper workflow execution.

What's the best way to create a PR from a feature branch and clean up after merging?▼

Create a PR from a feature branch and clean up post-merge by using the Skill to set up the branch, push it, and automatically delete the branch once the PR is merged and CI checks pass.

Does this approach to PR automation work for teams needing standardized governance?▼

Yes, this PR automation works for software development teams needing standardized governance. It provides deterministic PR lifecycles by applying consistent rules for creation, review enforcement, and merge conditions across the repository.

Why should I automate merging PRs instead of handling them manually?▼

Automating PR merging eliminates manual context switching and reduces human error. It ensures merges happen only after CI checks pass and approvals are met, providing a deterministic and standardized pull request lifecycle across your team.

Related Skills

Explore More Software Engineering Skills→
aivos-xieaivos-xie
1

github-pr-workflow

Automate the GitHub Pull Request lifecycle from branch creation to merging.

Community
Advanced
ITSaltITSalt
23

nacl-tl-release

Automate end-to-end software releases by merging PRs, validating CI, and publishing changelogs.

Community
Advanced
EmasoftEmasoft
1

amia-multilanguage-pr-review

Detect languages in PRs and apply language-specific linters with consolidated findings.

Community
Advanced
ZardLi1115ZardLi1115
4

github-pr-workflow

Guide GitHub pull requests from branch creation through CI monitoring and merge.

Community
Advanced