Menu
Use when creating a GitHub pull request or merge request from the current branch, especially when a project PR template may exist.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when asked to add a Changesets release note, create a .changeset markdown file, choose semver impact, or satisfy a missing changeset check before a pull request.
Generates interactive multi-page HTML codebase courses with Mermaid diagrams, architecture walkthroughs, module dependency tutorials, data-flow views, state-machine views, and per-module deep dives. Use when asked to teach, map, explain, or visually tour a repository.
Use when asked to analyze code and add explanatory code annotations, file headers, doc comments, inline comments, or JSX-safe comments.
Use when asked to quickly stage all current changes and commit them with an automatically selected commit message.
Use when asked to create, rewrite, audit, or maintain README, ARCHITECTURE, CONTRIBUTING, TUTORIAL, docs navigation, project options, badges, or documentation signatures.
| name | create-mr |
| description | Use when creating a GitHub pull request or merge request from the current branch, especially when a project PR template may exist. |
Create a GitHub pull request from the current branch by reading the repository state, respecting any PR template, and verifying the created PR.
Search for a PR template in this order:
.github/PULL_REQUEST_TEMPLATE.md.github/PULL_REQUEST_TEMPLATE/*.md (pick the first match)PULL_REQUEST_TEMPLATE.mddocs/PULL_REQUEST_TEMPLATE.mdIf a template is found, read it and use it as the base structure for the PR body. Preserve all template sections and fill them from the actual changes.
If no template is found, use the default body format below.
Run these checks, parallelizing file reads and git commands where possible:
git status
git diff --staged
git diff
git log --oneline -20
git remote -v
git branch --show-current
From the gathered context:
Title requirements:
<type>(<scope>): <short description>.Example:
feat(auth): add OAuth2 login flow
Default body when no template exists:
## Summary
- <1-3 bullets summarizing what this PR does>
## Changes
- <key change 1>
- <key change 2>
## Test Plan
- <how to verify these changes>
## Screenshots
<before/after for visual changes, or omit if not applicable>
Use GitHub CLI:
gh pr create --title "<title>" --body "<body>"
If the body is large, write it to a temporary file and pass --body-file.
If the current branch has no remote tracking branch, push first:
git push -u origin HEAD
Then retry gh pr create.
After creation, run:
gh pr view <number>
For machine-readable verification, prefer:
gh pr view <number> --json number,title,url,state,headRefName,baseRefName
Report the PR URL to the user.
| Mistake | Fix |
|---|---|
| Ignoring a PR template | Search all supported template locations first. |
| Writing a title from memory | Base the title on the actual diff and commits. |
| Claiming tests passed without evidence | Put only verified commands in the test plan. |
| Forgetting to push the branch | Push with git push -u origin HEAD, then create the PR. |