skills.rest
jlaws
jlawsCOMMUNITY
Explore all skills by this author →
GitHub

cmd-workflow-create-pr

Stage, commit, branch, push, and open a GitHub pull request.

2|Updated Jan 3, 2026
Search Tags:#automation#git#workflow#commit#github#branch#pull-request
One-click install
npx skills add https://github.com/jlaws/dotfiles --skill cmd-workflow-create-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cmd-workflow-create-pr
Source: https://github.com/jlaws/dotfiles/tree/main/.agents/skills/cmd-workflow-create-pr
Command: npx skills add https://github.com/jlaws/dotfiles --skill cmd-workflow-create-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the GitHub PR workflow — stage, commit, branch, push, and open a pull request for changes, reducing manual overhead and ensuring consistent review-ready PRs.

Core Features & Use Cases

  • Stage changes, create a feature branch, commit with a clear message, push to remote, and open a PR on GitHub for review.
  • Use in team development to enforce PR hygiene, traceability, and faster code reviews.
  • Use Case: A developer finishes a feature on a branch and uses this skill to automatically open a pull request with a descriptive title and body.

Quick Start

Run the workflow on the current repository after committing your changes to automatically create and open a PR on GitHub.

Frequently Asked Questions about cmd-workflow-create-pr

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 from the command line requires staging changes, committing, branching, pushing to remote, and opening a PR. This workflow handles that sequence end-to-end to ensure consistent review-ready PRs without manual overhead.

What is the standard git workflow for opening a pull request after committing changes?▼

The standard git workflow for opening a pull request involves staging changes, creating a feature branch, committing with a clear message, pushing to remote, and opening a PR on GitHub for review to maintain traceability and code review hygiene.

Do I need GitHub credentials to automate branch pushing and PR creation?▼

Yes, you need GitHub credentials to automate branch pushing and PR creation. The workflow requires access to Git and GitHub credentials to operate across repositories and successfully push commits and open pull requests.

Can I use an automated PR workflow for solo development projects?▼

Yes, you can use an automated PR workflow for solo development projects. This process supports standard PR workflows in both solo and team development to enforce consistent PR practices and reduce manual overhead.

What's the best way to enforce consistent PR practices across a development team?▼

The best way to enforce consistent PR practices is to automate the GitHub pull request creation process. By standardizing staging, committing, branching, and pushing, teams ensure traceability and faster code reviews with descriptive titles and bodies.

Related Skills

Explore More Software Engineering Skills→
githubgithub
37.6k

git-commit

Analyze git diffs to generate conventional commit messages and stage files.

Official
Intermediate
yanochka11yanochka11

iterate-pr

Iterate pull requests by resolving CI failures and review feedback until validation succeeds.

Community
Advanced
toqoztoqoz

github-release-pr

Automate GitHub release pull requests between development and production branches.

Community
Advanced
ianclearyiancleary
1

git-push-pr

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

Community
Intermediate