Claude-skill-registry gh-pr
Use this skill when creating a GitHub pull request. Defines PR body format with Why/What/Notes sections and ensures proper assignment.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/gh-pr" ~/.claude/skills/majiayu000-claude-skill-registry-gh-pr && rm -rf "$T"
manifest:
skills/data/gh-pr/SKILL.mdsource content
GitHub Pull Request Creation
When creating a pull request, use the
gh CLI with the following format and
conventions.
PR Body Format
## Why? [Explain the motivation for this change. What problem does it solve?] ## What? [Describe what was changed. List the key modifications.] ## Notes [Optional. Additional context, testing notes, or follow-up items.]
Command Template
gh pr create --assignee @me --title "<title>" --body "$(cat <<'EOF' ## Why? <motivation> ## What? <changes> ## Notes <optional notes> EOF )"
Rules
- Always assign PR to
using@me--assignee @me
- Required. Explain motivation and problem being solved## Why?
- Required. Describe the changes made## What?
- Optional. Include only if there are additional notes## Notes- Omit
section entirely if no notes are needed## Notes - Use imperative mood in title (e.g., "Add feature" not "Added feature")
- Keep title concise and descriptive
Example
gh pr create --assignee @me --title "Add user authentication" --body "$(cat <<'EOF' ## Why? Users need secure access to their accounts. Currently there is no authentication mechanism in place. ## What? - Add login/logout endpoints - Implement JWT token generation - Add password hashing with bcrypt - Create auth middleware for protected routes ## Notes Requires `JWT_SECRET` env variable to be set in production. EOF )"