gh-pr
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
## Why?
More from fredrikaverpil/dotfiles
golang-style
Use this skill BEFORE writing or editing any Go (.go) files. Triggers when
58gh-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.
42aip
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.
35git-commit
>-
33skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
32jira-cli
Jira CLI (`jira`) command reference. Use when working with Jira issues, epics, sprints, Jira ticket numbers, Jira URLs, or any Jira operations from the command line.
19