Menu
Create pull requests. Use when opening PRs, writing PR descriptions, or preparing changes for review.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
| name | create-pr |
| description | Create pull requests. Use when opening PRs, writing PR descriptions, or preparing changes for review. |
Create pull requests.
Requires: Git access and whatever PR creation mechanism your environment supports.
If your agent runtime provides a dedicated PR tool, use that instead of shelling out to gh pr create. Treat this file as a workflow checklist, not a requirement to use a specific tool.
git branch --show-current
IMPORTANT: If you are on main or master, you MUST create a feature branch before committing:
# Create and switch to a feature branch
git checkout -b <feature-branch-name>
Use your environment's branch naming policy. If the repo or runtime specifies a required prefix/suffix, follow that instead of inventing a new pattern. Otherwise, use a descriptive branch name such as:
feat/add-user-authenticationfix/null-pointer-in-parserrefactor/extract-helper-functionsNever commit directly to main/master when preparing a PR.
# Check for uncommitted changes
git status --porcelain
If there are uncommitted changes, stage and commit them:
git add <files>
git commit -m "<type>(<scope>): <description>"
# Push branch to remote (creates it if needed)
git push -u origin $(git branch --show-current)
# Verify commits that will be in the PR
git log origin/main..HEAD --oneline
Ensure:
Review what will be included in the PR:
# See all commits that will be in the PR
git log origin/main..HEAD
# See the full diff
git diff origin/main...HEAD
Understand the scope and purpose of all changes before writing the description.
Follow this structure:
<brief description of what the PR does>
<why these changes are being made - the motivation>
<alternative approaches considered, if any>
<any additional context reviewers need>
Do NOT include:
Do include:
Create the PR using your environment's approved mechanism:
gh pr create only when shell-based PR creation is actually supported and allowedRegardless of mechanism, use the same title/body guidance from this skill and make sure the branch has already been pushed.
Title format follows commit conventions:
feat(scope): Add new featurefix(scope): Fix the bugref: Refactor somethingchore: Minor changeBasé sur la classification professionnelle SOC
Address PR review comments following test-driven approach. Use when fixing issues raised in code reviews.
Reference for StyleX style authoring patterns, constraints, and APIs. Use when generating StyleX output code, writing stylex.create() styles, applying stylex.props(), working with themes/variables, pseudo-classes, media queries, dynamic styles, or debugging StyleX-related transformation issues in the codemod.
Remove code duplication, extract shared patterns, and eliminate type casts and `any` types. Run after implementing new features.
