If you work in a Sentry codebase, this wraps the GitHub CLI to enforce their PR conventions: conventional commit titles, descriptions that explain motivation over test plans, and proper issue references. It walks you through verifying your branch state, analyzing the diff, and writing a description that actually helps reviewers understand why you made these changes. The examples are pulled straight from Sentry's internal guidelines, so you get the feat/fix/ref prefixes right and skip the checkbox theatre they explicitly don't want. Useful if you're contributing to Sentry or want to adopt similar conventions for your own team.
npx skills add https://github.com/davila7/claude-code-templates --skill create-pr