skills.rest
brandonalfred
brandonalfredCOMMUNITY
Explore all skills by this author →
Website𝕏@brandonalfred_GitHub

pr

Automate Git commits, branch pushes, and pull request creation.

2|Updated Feb 3, 2026
Search Tags:#git#workflow#commit#github#branch-management#pull-request
One-click install
npx skills add https://github.com/brandonalfred/fortuna-app --skill pr-brandonalfred
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/brandonalfred/fortuna-app/tree/main/.claude/skills/pr
Command: npx skills add https://github.com/brandonalfred/fortuna-app --skill pr-brandonalfred

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the Git workflow for committing changes, pushing a feature branch, and creating a pull request, reducing manual steps and human error.

Core Features & Use Cases

  • Branch-aware commits: ensures on a feature branch and enforces conventional commit prefixes (feat:, fix:).
  • Push workflow: pushes the branch to origin with upstream tracking.
  • PR creation: creates a PR against the main branch with a clear title and description, ready for review.
  • Use Case: A developer finishes a feature on a dedicated branch and uses this workflow to open a PR quickly.

Quick Start

On a feature branch, commit your changes, push the branch to origin, and automatically open a PR with a descriptive title.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate git workflow to commit, push, and create a pull request?▼

Automating git workflow involves committing changes with conventional prefixes, pushing the feature branch to origin with upstream tracking, and generating a pull request against the main branch. This reduces manual steps and human error.

What is a conventional commit prefix and when do I need it for a pull request?▼

A conventional commit prefix like feat: or fix: categorizes your changes. You need it when your git workflow requires structured commit messages to maintain clear project history and generate standardized pull request titles for review.

How do I push a feature branch to origin with upstream tracking?▼

To push a feature branch with upstream tracking, the workflow pushes your current branch to origin and sets the remote branch for tracking. This ensures future git push and git pull commands map directly to your remote feature branch.

Does this pull request workflow require a specific branch management strategy?▼

Yes, this pull request workflow enforces an on-feature-branch strategy, ensuring you are not committing directly to main. It requires a dedicated feature branch to properly manage branch naming and create the PR against the main branch.

Can I use this to create a pull request against branches other than main?▼

No, this workflow specifically creates a pull request against the main branch with a structured description. It guides branch naming and formats the PR for the main repository branch to ensure consistent integration.

What is the best way to format a pull request description for GitHub repositories?▼

The best way to format a pull request description is using a structured template generated from your conventional commit history. This ensures the PR title and description clearly communicate the feature changes for GitHub repository review.

Related Skills

Explore More Software Engineering Skills→
simorgh3196simorgh3196
1

using-git-worktrees

Create isolated git worktrees and run project setup steps.

Community
Basic
cookeyholdercookeyholder

squash-pr

Squash and merge a GitHub pull request into main after validating review feedback.

Community
Advanced
ComputerConnectionComputerConnection

ship

Automate release workflows by merging, testing, reviewing diffs, bumping versions, and opening pull requests.

Community
Advanced
ianclearyiancleary
1

git-push-pr

Automate Git staging, committing, pushing, and pull request management with GitHub CLI.

Community
Intermediate