Generates pull requests with standard titles and body formatting based on current git status.
Install
mkdir -p .claude/skills/pr-mengchaoheng && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17359" && unzip -o skill.zip -d .claude/skills/pr-mengchaoheng && rm skill.zipInstalls to .claude/skills/pr-mengchaoheng
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.
Create a pull request with conventional commit title and descriptionKey capabilities
- →Create a pull request
- →Use conventional commit titles
- →Use conventional commit descriptions
- →Perform sanity builds for hardware and simulation targets
- →Format PR body concisely
How it works
The skill checks the current branch, gathers context, performs sanity builds, and then creates a pull request with a conventional title and description.
Inputs & outputs
When to use pr
- →Submit feature branch for review
- →Automate PR creation
- →Verify build before opening PR
About this skill
PX4 Pull Request
No Claude attribution anywhere (no Co-Authored-By, no "Generated with Claude").
Steps
-
Check branch. If on
main, create a feature branch<username>/<description>where<username>comes fromgh api user --jq .login. -
Gather context:
git status,git log --oneline main..HEAD,git diff main...HEAD --stat, check for remote tracking branch. -
Sanity-build the targets we care about. Fix any build errors before opening the PR:
make px4_fmu-v6x— hardware targetmake px4_sitl— simulation
-
PR title:
type(scope): description— under 72 chars, covers the overall change across all commits. This becomes the squash-merge commit message. -
PR body: start with a plain leading paragraph explaining what the PR does and why. No headings (
## Summary,## Test plan, etc.), no boilerplate, no Claude attribution. Use bullet lists only to enumerate discrete changes; don't force prose into bullets. Describe testing inline if relevant, no separate test plan section. Use markdown (links, code blocks, lists) only when warranted. Keep it concise and well-formatted. -
Push with
-uif needed, thengh pr create. Default base ismainunless user says otherwise. -
Return the PR URL.
If the user provided arguments, use them as context: $ARGUMENTS
When not to use it
- →When the user wants Claude attribution in commit messages or PR descriptions
- →When the user is on the `main` branch and does not want a feature branch created
Limitations
- →The skill does not include Claude attribution in PR artifacts
- →The skill creates a feature branch if on `main`
How it compares
This skill automates PR creation with built-in sanity checks and conventional formatting, unlike manually drafting and submitting a PR.
Compared to similar skills
pr side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| pr (this skill) | 0 | 3mo | 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.
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.