Agent skill · writing content · aiskillstore
commit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Why this skill is useful
Codifies Sentry-specific commit message conventions that the AI could infer but doesn't have to guess.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Sentry Commit Messages Follow these conventions when creating commits for Sentry projects. When to Use This Skill Use this skill when: Committing code changes Writing commit messages Formatting git history Following Sentry commit conventions Referencing Sentry issues in commits Prerequisites Before committing, ensure you're working on a feature branch, not the main branch. If you're on main or master, create a new branch first: Branch naming should follow the pattern: <type>/<short-description> where type matches the commit type (e.g., feat/add-user-auth, fix/null-pointer-error, ref/extract-validation). Format 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 Subject Line Rules Use imperative, present tense: "Add feature" not "Added feature" Capitalize the first letter No period at the end Maximum 70 characters Body Guidelines Explain what and why, not how Use imperative mood and present tense Include motivation for the change Contrast with previous behavior when relevant Footer: Issue References Reference issues in the footer using these patterns: Fixes closes the issue when merged Refs links without closing AI-Generated Changes When changes were primarily generated by a coding agent (like Claude Code), include the Co-Authored-By attribution in the commit footer: This is the only indicator of AI involvement that should appear in commits. Do not add phrases like "Generated by AI", "Written with Claude", or similar markers in the subject, body, or anywhere else in the commit message. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/commit--3697d3