Menu
Create or update a GitHub PR using the repo's pull_request_template.md format. Use when creating a new PR or updating an existing PR body.
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
Trigger when implementing any new feature, hook, or component — decisions about where to put new files and how to import them must follow these rules. Also trigger when adding imports.
Trigger when implementing, designing, or modifying any React component or hook — including planning new components before any file is touched. Enforces styling and naming conventions that OVERRIDE default React patterns.
Trigger when testing is any part of the task — writing tests, adding coverage, adding test cases, or implementing code that will need tests. Project-specific mocking rules that OVERRIDE standard defaults.
Update Michelangelo documentation. Use when adding, modifying, or fixing docs in the docs/ folder. Ensures consistent formatting, proper titles, and valid links.
Create a 3-agent team (engineer, tech-writer, product-manager) to review and improve docs for open-source quality. Use when reviewing any docs/ directory or specific doc files.
Trigger when implementing anything in .ts or .tsx — new types, interfaces, hooks, or any feature that will involve TypeScript decisions. Don't wait for type errors; consult this before writing types, not after. Covers patterns that OVERRIDE TypeScript defaults.
| name | pr-template |
| description | Create or update a GitHub PR using the repo's pull_request_template.md format. Use when creating a new PR or updating an existing PR body. |
| user-invocable | true |
Create or update a GitHub PR following the repo's pull request template.
Read the template from .github/pull_request_template.md and use it as the exact structure for the PR body.
git diff main...HEAD (or git diff HEAD~1 if already on main) to understand the changesgit push -u origin <branch>gh pr create --title "<title>" --body "<body>"gh pr view --json number -q '.number'gh pr edit <number> --body "<body>"<type>(<scope>): <short description>feat, fix, docs, ci, refactor, chore, test, perfpython, helm, ci, npm, ui, godocs(contributing): add PR template skill, ci(release): add PyPI publishing stepBREAKING CHANGE: footer or ! suffix in the commit.