Commit

If you work in the Sentry codebase or want to adopt their commit conventions, this skill handles the formatting for you. It knows the full spec: conventional commits with types like feat, fix, and ref, scoped headers under 100 characters, and Sentry-specific issue references (GH-1234, SENTRY-5678, LINEAR-ABC-123). The nice thing is it doesn't just template out the format. It knows when to use Fixes versus Refs, how to structure breaking changes, and the imperative mood rules that everyone forgets. Saves you from checking the docs every time you need to write a proper commit message.

skills.sh installs: 435
GitHub stars: 33.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add davila7/claude-code-templates --skill commit --agent claude-code

Installs into .claude/skills of the current project.

Files

Sentry Commit Messages

Follow these conventions when creating commits for Sentry projects.

Format

<type>(<scope>): <subject>

<body>

<footer>

The header is required. Scope is optional. All lines must stay under 100 characters.

Commit Types

Type	Purpose
`feat`	New feature
`fix`	Bug fix
`ref`	Refactoring (no behavior change)
`perf`	Performance improvement
`docs`	Documentation only
`test`	Test additions or corrections
`build`	Build system or dependencies
`ci`	CI configuration
`chore`	Maintenance tasks
`style`	Code formatting (no logic change)
`meta`	Repository metadata
`license`	License changes