Provides conventions for branch naming, PR titles, and issue linking to maintain project discipline.
Install
mkdir -p .claude/skills/pr-microsoft && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18720" && unzip -o skill.zip -d .claude/skills/pr-microsoft && rm skill.zipInstalls to .claude/skills/pr-microsoft
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Guidance for branch naming, commit messages, and PR titles.Key capabilities
- →Create a new branch with a specified naming convention
- →Format pull request titles using Conventional Commits prefixes
- →Link pull requests to GitHub issues using keywords
- →Write commit messages in an imperative style
- →Remove co-author lines from pull request descriptions
How it works
The skill provides guidelines for naming branches, formatting commit messages, and structuring pull request titles and descriptions. It specifies prefixes for PR titles and keywords for linking issues.
Inputs & outputs
When to use pr
- →Name a new development branch
- →Format pull request titles
- →Link PRs to issues
- →Standardize commit messages
About this skill
Pull Request Conventions
Branch discipline
- Never commit to
maindirectly. Create a branch:<user>/<short-description>(e.g.mmansour/optimize-handler-allocs). - One logical change per commit. Write imperative messages: "Add …" not "Added …".
PR title format
PR titles must use a Conventional Commits prefix:
| Prefix | When to use | Example |
|---|---|---|
feat: | New feature or capability | feat: add HTTP/2 support to hyper example |
fix: | Bug fix | fix: render missing signals as empty |
chore: | Maintenance, refactoring, CI, docs, dependencies | chore: move shared files to examples/app |
The prefix is lowercase, followed by a colon and a space, then a short imperative description.
Linking PRs to issues
When a PR is meant to close a GitHub issue, include the keyword Closes followed by the issue number in the PR description body (not the title):
Closes #42
For multiple issues, use one per line:
Closes #42
Closes #43
Note: Issue-linking keywords only work when the PR targets the repository's default branch. See GitHub docs: linking a pull request to an issue for the full reference.
PR description
Remove the Co-author-by line from the PR description. If you want to credit a co-author, add them as a reviewer instead. And check all the changes from its merge-base to get a detailed summary for the commit.
Framework change PRs
For PRs touching core framework code (handler, parser, protocol, router, CLI runtime, FFI), apply the code-review skill checklist before opening the PR. It covers correctness, concurrency, performance, design, and style checks that complement the automated quality gate.
When not to use it
- →When committing directly to the `main` branch
- →When a pull request does not target the repository's default branch for issue linking
Limitations
- →Issue-linking keywords only work when the PR targets the repository's default branch
- →The skill does not cover all aspects of pull request creation, such as code review checklists for framework changes
How it compares
This skill provides explicit rules for development workflow elements, unlike a manual approach where naming and formatting conventions might be inconsistent or absent.
Compared to similar skills
pr side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| pr (this skill) | 0 | 4mo | No flags | Beginner |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
| dependency-upgrade | 26 | 4mo | Review | Intermediate |
| git-commits | 21 | 3mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by microsoft
View all by microsoft →You might also like
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
git-commits
bonny
Create well-structured git commits in logical chunks following best practices
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
github-multi-repo
ruvnet
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration
git-workflow-enforcer
CrazyDubya
Ensures commits follow conventional commits, branch naming conventions, and PR templates. Use when creating commits, branches, or PRs, or when user mentions git workflow.