ReddRadar
Agent skill
gh-pr
This skill should be used when creating a GitHub pull request via `gh pr create`. Defines PR body format with Why/What/Notes sections, ensures proper assignment, and prompts for Jira ticket number.
Install this agent skill to your Project
npx add-skill https://github.com/fredrikaverpil/dotfiles/tree/main/stow/shared/.claude-work/skills/gh-pr
SKILL.md
GitHub Pull Request Creation
When creating a pull request, use the gh CLI with the following format and
conventions.
- Always create draft PRs.
- Keep PR titles, descriptions, and comments concise and clear.
- Include only useful information. Remove redundancy and over-explanation.
- Prefer explicitness and clarity over verbosity.
PR title format
Write the title as if the whole PR was squashed into a single commit using conventional commits.
PR Body Format
# XY-123
## 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 --draft --assignee @me --title "<title>" --body "$(cat <<'EOF'
## Why?
<motivation>
## What?
<changes>
## Notes
<optional notes>
EOF
)"
Rules
- Always assign PR to
@meusing--assignee @me # XY-123- Always ask the user for the Jira ticket number before creating the PR. If there is one, include it as an H1 header at the top of the body. If there isn't one, omit it.## Why?- Required. Explain motivation and problem being solved## What?- Required. Describe the changes made## Notes- Optional. Omit entirely if no notes are needed- Use imperative mood in title (e.g., "Add feature" not "Added feature")
- Keep title concise and descriptive
Example
gh pr create --draft --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
)"
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
fredrikaverpil/dotfiles
golangci-lint
When linting is failing.
fredrikaverpil/dotfiles
git-commit
This skill should be used BEFORE running any git commit command. Triggers when about to run `git commit`. Ensures commit messages follow Conventional Commits specification and prompts for Jira ticket number.
fredrikaverpil/dotfiles
neovim
fredrikaverpil/dotfiles
gh-cli
GitHub CLI (gh) command reference. Use when working with GitHub repositories, PRs, issues, actions, `gh api`, or any GitHub operations from the command line.
fredrikaverpil/dotfiles
git-commit
This skill should be used BEFORE running any git commit command. Triggers when about to run `git commit`. Ensures commit messages follow Conventional Commits specification.
fredrikaverpil/dotfiles
aip
Google API Improvement Proposals (AIP) reference. Use BEFORE designing or reviewing APIs, protobuf definitions, or any work involving Google API design standards. Fetches relevant AIP rules from https://google.aip.dev for the task at hand.
Didn't find tool you were looking for?