skills.rest
so-ota-biz
so-ota-bizCOMMUNITY
Explore all skills by this author →
GitHub

pr-create

Create GitHub MCP pull requests from the checked-out branch with a template-based body.

Updated Aug 23, 2026
Search Tags:#automation#workflow#diff#pr#pull-request#conventional-commits#github-mcp
One-click install
npx skills add https://github.com/so-ota-biz/ai-agent-orchestration-settings --skill pr-create-so-ota-biz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-create
Source: https://github.com/so-ota-biz/ai-agent-orchestration-settings/tree/main/.agent/skills/pr_create
Command: npx skills add https://github.com/so-ota-biz/ai-agent-orchestration-settings --skill pr-create-so-ota-biz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates creating GitHub MCP pull requests from the currently checked-out branch, assembling a fact-based body from a template and avoiding automatic commits or pushes.

Core Features & Use Cases

  • Create PRs from the active branch using GitHub MCP.
  • The PR body is generated from a standard template and includes a diff summary and a conventional-commits style title.
  • Ensures pre-approval is obtained before PR creation and applies the repository's workflow.

Quick Start

With your current branch checked out, invoke the pr-create skill and approve the PR before it is opened.

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 pull request from my current branch?▼

You can automate pull request creation by using GitHub MCP to assemble a fact-based body from the repository's PR template and a diff summary, requiring pre-approval before opening the PR.

Does the PR generation workflow enforce conventional commits?▼

Yes, the PR generation workflow enforces conventional commits by applying this style to the PR title, ensuring standardized naming conventions based on the branch diff.

Can I generate a PR body from a template without pushing commits?▼

Yes, you can generate a PR body from a template without pushing commits because the workflow avoids automatic commits or pushes, deferring those actions while assembling the pull request.

What is the best way to ensure a standardized PR title and body based on a diff?▼

The best way to ensure a standardized PR title and body based on a diff is to use an automated workflow that generates a conventional-commits title and assembles the body from the repository's PR template.

Do I need to manually approve the pull request before it is created via MCP?▼

Yes, you need to manually approve the pull request before it is created, as the workflow enforces pre-approval to review the generated title and body before submission to GitHub MCP.

When should I not use automated PR creation for my branch?▼

You should not use automated PR creation when your branch is not yet ready for review, as the workflow assumes the branch is finalized and defers commit and push actions rather than handling them automatically.

Related Skills

Explore More Software Engineering Skills→
bastani-incbastani-inc
484

gh-create-pr

Commit unstaged changes, push the branch, and create a pull request.

Official
Advanced
catu-aicatu-ai
12

harness-land

Merge an approved pull request after confirming an archived harness plan.

Official
Intermediate
mhattingpetemhattingpete
657

git-pushing

Stage, commit, and push code changes with conventional commit messages.

Community
Basic
tranhieutttranhieutt
70

pr-writer

Generate GitHub pull request titles and bodies following conventional commit conventions.

Community
Intermediate