create-pull-request

Generate GitHub pull request titles and bullet-only bodies via gh pr create.

2|Updated Jun 1, 2017
One-click install
npx skills add https://github.com/carlos-algms/dotfiles --skill create-pull-request-carlos-algms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pull-request
Source: https://github.com/carlos-algms/dotfiles/tree/main/AI-configs/skills/create-pull-request
Command: npx skills add https://github.com/carlos-algms/dotfiles --skill create-pull-request-carlos-algms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents accidental or ambiguous GitHub pull request creation by enforcing a clear user-request gate and a consistent PR title/body format.

Core Features & Use Cases

  • Explicit visibility gate: only creates a PR when the user clearly requests it (compose-only path for “just draft the content”).
  • Canonical PR formatting: generates a conventional title and a bullet-only markdown body with strict rules for structure and markdown style.
  • Branch-aware workflow: compares the branch against the chosen base branch to inform a complete PR description rather than just the latest commit.
  • Safety constraints: blocks forbidden actions like history rewrites before PR and avoids adding co-author or AI attribution footers.

Quick Start

Ask for an open draft or ready pull request and include the intent to create it (for example: open PR / draft PR / ship PR), and the skill will show the exact title and bullet-only body before running gh pr create.

Frequently Asked Questions about create-pull-request

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

FAQPage Schema
How do I create a GitHub pull request with a properly formatted title and body?

To create a GitHub pull request with a properly formatted title and body, you can use a skill that enforces a conventional title and a bullet-only markdown body, passing the content via stdin heredoc to gh pr create.

What is the best way to draft a PR from a git branch diff without adding AI attribution footers?

Drafting a PR from a git branch diff without adding AI attribution footers requires a tool that blocks forbidden footers and compares the full branch history against the base branch to generate the description.

Can I generate pull request content without actually opening the PR on GitHub?

Yes, you can generate pull request content without opening the PR by using a compose-only path that requires explicit user intent, ensuring the PR is only created when you clearly request it.

How does branch diff comparison improve pull request descriptions compared to using only the latest commit?

Branch diff comparison improves pull request descriptions by analyzing the full commit history and differences against the chosen base branch, resulting in a complete PR description rather than one based solely on the latest commit.

Does creating a pull request this way rewrite git history or modify the branch?

No, creating a pull request this way does not rewrite git history or modify the branch, as the workflow enforces safety constraints that block history rewrites before PR creation.

Why are bullet-only bodies recommended for GitHub pull request formatting?

Bullet-only bodies are recommended for GitHub pull request formatting because they enforce strict markdown style rules and structural constraints, ensuring the PR description remains clear and consistent.