pr-create

Stage changes, create conventional commits, push with force-with-lease, and open a pull request via gh CLI.

Updated Jul 3, 2025
One-click install
npx skills add https://github.com/andrew-t-james/dotfiles --skill pr-create-andrew-t-james
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-create
Source: https://github.com/andrew-t-james/dotfiles/tree/main/dot_claude/skills/pr-create
Command: npx skills add https://github.com/andrew-t-james/dotfiles --skill pr-create-andrew-t-james

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stage changes, create semantic commits, push with force-with-lease, and open a pull request using the GitHub CLI to streamline code reviews and collaboration.

Core Features & Use Cases

  • Stage changes, generate conventional commits, push with force-with-lease, and open a PR via gh CLI.
  • Supports selecting a base branch, marking PRs as draft, and overriding commit scopes for consistent reviews across multiple files or modules.
  • Use cases include finishing a feature on a branch and quickly opening a PR ready for teammate feedback.

Quick Start

Instruct the agent to prepare and open a PR on the current repository with a base branch and a descriptive title.

Frequently Asked Questions about pr-create

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

FAQPage Schema
How do I automate creating a GitHub pull request from the command line?

Automating a GitHub pull request requires staging changes, creating semantic commits, pushing with force-with-lease, and using the gh CLI to open the PR. This workflow resolves the base branch and drafts the PR for teammate review.

How do I create conventional commits before pushing a feature branch?

Creating conventional commits involves staging your changes and generating a semantic commit message with an optional scope override. This ensures consistent formatting before pushing the feature branch to GitHub.

Does the gh CLI support opening draft pull requests for feature branches?

Yes, the gh CLI supports opening draft pull requests for feature branches. You can select a base branch, resolve the target, and mark the PR as a draft to signal work-in-progress to reviewers.

What is the safest way to force push a Git branch during release prep?

The safest way to force push a Git branch during release prep is using force-with-lease. This prevents overwriting remote changes by checking that the remote branch matches your local tracking branch before pushing.

Can I override commit scopes when staging multiple files for a PR?

Yes, you can override commit scopes when staging multiple files or modules for a PR. This allows you to generate conventional commits with customized scopes, ensuring consistent reviews across different parts of the repository.

Why does GitHub workflow automation require base-branch resolution for PR creation?

GitHub workflow automation requires base-branch resolution to ensure the PR targets the correct integration branch. Resolving the base branch prevents merging code into the wrong release line and maintains clean repository history.