pull-request

Automate the full pull request workflow from branch creation to PR opening.

2.6k|194|Updated Sep 12, 2025
One-click install
npx skills add https://github.com/heyitsnoah/claudesidian --skill pull-request-heyitsnoah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/heyitsnoah/claudesidian/tree/main/.agents/skills/pull-request
Command: npx skills add https://github.com/heyitsnoah/claudesidian --skill pull-request-heyitsnoah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the end-to-end pull request workflow to reduce manual steps from creating a feature branch to opening a PR after commits.

Core Features & Use Cases

  • Create a feature branch from a user-provided description or title.
  • Stage, commit with a conventional message, push to the remote, and open a PR with a detailed description.
  • Safeguards include pre-checks for repository status, branch conflicts, and PR existence, plus guidance for reviewers.

Quick Start

Create a feature branch, commit changes with a descriptive message, push to GitHub, and open a pull request.

Frequently Asked Questions about pull-request

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

FAQPage Schema
How do I automate the pull request workflow from branch creation to opening a PR?

You can automate the pull request workflow by using a tool that creates a feature branch, commits changes with conventional messages, pushes to the remote, and opens a PR. This eliminates manual steps from branch creation to PR opening.

What is the best way to ensure conventional commits are used when automating a pull request?

The best way to ensure conventional commits is to use an automation tool that applies them during the commit phase. This Skill automatically generates and applies conventional commit messages as part of the end-to-end PR workflow.

Does the GitHub CLI support end-to-end pull request automation with safeguards?

Yes, the GitHub CLI supports end-to-end pull request automation with safeguards. This Skill utilizes the GitHub CLI to handle changes, commits, and review processes while implementing pre-checks for repository status and branch conflicts.

What pre-checks are needed before automating branch management for a pull request?

Required pre-checks for branch management include verifying repository status, checking for branch conflicts, and confirming an existing PR is not already open. These safeguards prevent errors during the automated pull request workflow.

Can I automatically generate a PR description and provide reviewer guidance for Git repositories?

Yes, you can automatically generate a PR description and provide reviewer guidance. This automation handles PR opening with a detailed description and includes guidance for reviewers as part of the pull request workflow.