create-pr

Create GitHub pull requests with commit messages and issue links.

Updated Aug 27, 2026

Search Tags:#automation #git #commit #branch #pr #pull-request

Ready to run

npx skills add https://github.com/satriachandrayw/skills --skill create-pr-satriachandrayw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/satriachandrayw/skills/tree/main/create-pr/skills/create-pr
Command: npx skills add https://github.com/satriachandrayw/skills --skill create-pr-satriachandrayw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Completing work often ends without a clean PR workflow: developers forget to stage changes, create informative PRs, or link issues. This skill automates PR creation to streamline handoffs from code completion to review.

Core Features & Use Cases

Auto-detects unstaged changes and commits them with conventional-type messages.
Gathers git context (branch, ahead/behind, changed files) and links related issues.
Generates a structured PR body and pushes via gh, including deployment checklists and optional migrations.

Quick Start

Ask Claude Code to create a PR after tests pass and changes are staged.

Frequently Asked Questions about create-pr

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

FAQPage Schema

How do I create a pull request automatically from unstaged git changes?▼

To create a pull request automatically, this skill detects unstaged changes, commits them with conventional messages, gathers branch context, and pushes a structured PR via GitHub CLI.

How do I automate linking issues when creating a PR from the command line?▼

Automating issue linking during PR creation involves gathering git context to detect related issues from commit history, then embedding those links into the structured PR body before pushing via gh.

What is the best way to generate a PR body with a deployment checklist?▼

Generating a PR body with a deployment checklist requires gathering git context and changed files, then producing a structured PR body that includes deployment steps and optional migrations via gh.

Do I need the GitHub CLI to push a PR from completed local work?▼

Yes, GitHub CLI integration is required to push the PR from your local branch to the remote repository after generating the structured PR body and detecting change context.

Can I create a PR before staging my changes?▼

Yes, you can create a PR before staging because this skill auto-detects unstaged changes and commits them with conventional-type messages as part of the automated PR workflow.

Does this PR automation check for existing pull requests before pushing?▼

Yes, this PR automation performs existing-PR checks before pushing, ensuring it does not create duplicate pull requests when a PR for the current branch already exists.