skills.rest
buddypia
buddypiaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

create-pr

Automate Git pull request creation from feature branches to develop.

Updated Feb 21, 2026
Search Tags:#automation#git#workflow#ci/cd#pull request#github
One-click install
npx skills add https://github.com/buddypia/kaiju-voice --skill create-pr-buddypia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/buddypia/kaiju-voice/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/buddypia/kaiju-voice --skill create-pr-buddypia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the entire process of creating a pull request from a feature branch to the develop branch, including commits, pushing, and merging, streamlining your Git workflow.

Core Features & Use Cases

  • Full Automation: Handles branch switching, staged file checks, commit creation, pushing, PR creation, and squashing/merging into develop.
  • Safety Checks: Prevents commits with sensitive files and ensures proper branch states.
  • Release Mode: Supports creating PRs from develop to master without automatic merging.
  • Use Case: After completing a new feature, simply run create-pr to automatically prepare, push, and merge your changes into the main development branch, saving significant manual Git operations.

Quick Start

Run the create-pr skill to automatically create a pull request for your staged changes.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate a git pull request from a feature branch to develop?▼

To automate a git pull request, this Skill handles branch switching, staged file validation, Conventional Commits generation, pushing, PR creation via GitHub CLI, and squashing merges directly into the develop branch.

How does Conventional Commits integration work for automated PRs?▼

Conventional Commits integration works by automatically generating your commit message based on staged files before pushing and creating the pull request, ensuring standardized commit histories without manual input.

Does this PR automation tool support release workflows to master?▼

Yes, this PR automation tool supports release workflows by providing a specific mode to create pull requests from develop to master without automatically merging the changes.

Can I use GitHub CLI to create a PR and squash merge in one step?▼

Yes, you can use GitHub CLI to create a PR and squash merge in one step, as the Skill orchestrates PR creation and executes the squashing merge into the develop branch automatically.

What safety checks prevent sensitive files in automated pull requests?▼

Safety checks prevent sensitive files in automated pull requests by validating staged files and ensuring proper branch states before generating commits and pushing changes.

What are the limitations of automating Git workflows for pull requests?▼

A limitation of automating Git workflows is that automatic merging is restricted to the develop branch, while release PRs to master are created without auto-merging, requiring manual approval for production deployments.

Related Skills

Explore More Software Engineering Skills→
mgoodman60mgoodman60

commit

Generate descriptive Git commit messages from repository changes with conventional formatting.

Community
Basic
messebmesseb

cicd

Manage GitHub release pipelines from develop branches to production tags.

Community
Advanced
CodySwannGTCodySwannGT
3

git-commit

Create conventional Git commits for staged changes with enforced branch naming.

Community
Intermediate
HuskyDannyHuskyDanny

github-pr-workflow

Automate GitHub pull request lifecycle using gh CLI and git commands.

Community
Advanced