git:pr

Creates GitHub pull requests with conventional commit titles and structured bodies.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/kellymears/agents --skill git-pr-kellymears
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git:pr
Source: https://github.com/kellymears/agents/tree/main/plugins/git/skills/git-pr
Command: npx skills add https://github.com/kellymears/agents --skill git-pr-kellymears

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a good pull request takes time — you need to survey the branch, summarize every meaningful change, link related issues, and give reviewers concrete verification steps. This Skill automates that entire drafting process so your PRs are consistent, honest, and easy to review. ## Core Features & Use Cases - Branch Survey: Inspects the current branch, commits since diverging from main, changed files, and open GitHub issues to ground the PR in real context. - Conventional Commit Titles: Generates titles in type(scope): description format (feat, fix, refactor, docs, and more) matching your commit history. - Structured PR Body: Produces a body with a two-sentence summary, optional Closes: #issue line, a Why section, a grouped What Changed checklist, and actionable Verification steps. - Team Announcement: After creating the PR via gh pr create, it writes a short, peer-toned announcement you can paste into Slack or release notes. - Use Case: You finished a feature branch with six commits. Ask to open a PR, review the drafted title and body, confirm, and get back the PR URL plus a ready-to-share announcement. ## Quick Start Ask the assistant to open a pull request for the current branch against main and confirm the drafted title and body before it is created.

Frequently Asked Questions about git:pr

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

FAQPage Schema
How do I create a pull request from the command line?▼

Use the GitHub CLI with `gh pr create --title "type(scope): description" --body "..."` after pushing your branch with `git push -u origin <branch>`. This Skill automates both steps and drafts the title and body for you.

How to write a good pull request title and description?▼

Use conventional commit format for the title, such as `feat(auth): validate session tokens`. The body should include a two-sentence summary, a Why section, a grouped list of changed files, and concrete verification steps reviewers can follow.

Can I open a pull request directly from the main branch?▼

No, this Skill refuses to open a PR against main from main and asks you to create or name a feature branch first. This protects the default branch and keeps review history clean.

Does gh pr create automatically link GitHub issues?▼

The PR body can include a `Closes: #issue` line that auto-links and closes the issue on merge. This Skill checks branch names, commit messages, and open issues, and asks you to confirm before adding the reference.

What safety rules apply when pushing and opening PRs?▼

The Skill never force pushes, never skips hooks with `--no-verify`, and never commits secrets like `.env` files or tokens. It also requires your confirmation of the drafted title and body before creating anything.