Sentry Commit Messages
FreeStreamline your commit process with Sentry conventions.
Free · Opens the source repo
What Sentry Commit Messages does
The Sentry Commit Messages skill is designed to enforce best practices when committing code changes, particularly for projects that utilize Sentry for error tracking. By following Sentry's conventions, this skill ensures that commit messages are structured correctly and contain necessary references to issues, which facilitates better tracking and understanding of changes in the codebase. This is particularly beneficial for teams that prioritize clean commit histories and effective collaboration.
When you trigger a commit, the skill checks the current branch to ensure that you are not committing directly to main or master, thus promoting safer development practices. If you are on a protected branch, the skill will automatically create a feature branch for you, streamlining the process and reducing the risk of accidental direct commits. This feature is crucial for maintaining branch safety and adhering to organizational policies regarding code contributions.
The skill also implements a strict format for commit messages, requiring a header, optional scope, body, and footer. This structure not only helps in maintaining consistency across commits but also aids in automatically linking issues to commits, which can enhance project management and tracking. The guidelines for writing the subject line and body of the commit message ensure that the messages are informative and follow a clear, imperative style.
Overall, this skill is ideal for developers and teams who want to maintain high standards in their commit practices, particularly in environments where Sentry is used for monitoring and error tracking. By automating the adherence to these conventions, the skill saves time and reduces the cognitive load associated with manual commit message formatting.
When to use it
Use this skill whenever you are preparing to commit code changes, especially in Sentry projects that require specific commit message formats.
When not to use it
This skill may not be suitable for projects that do not follow Sentry conventions or for users who prefer a more flexible commit message structure.
What you can build with it
Committing a bug fix
When fixing a bug in your application, use this skill to ensure your commit message follows the proper format and references the relevant issue.
Creating a new feature branch
If you need to add a new feature, this skill will automatically create a feature branch for you and format your commit message accordingly.
Maintaining commit history
Use this skill to keep your commit history clean and organized by enforcing structured commit messages that detail what changes were made.
How to install Sentry Commit Messages
View source1. Install with the skills CLI
npx skills add sickn33/agentic-awesome-skills/commit --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by sickn33Sentry Commit Messages
Follow these conventions when creating commits for Sentry projects.
When to Use
- The user asks to commit code, prepare a commit message, or save changes in git.
- You need Sentry-style commit formatting with conventional commit structure and issue references.
- The task requires enforcing branch safety before committing, especially avoiding direct commits on
mainormaster.
Prerequisites
Before committing, always check the current branch:
git branch --show-current
If you're on main or master, you MUST create a feature branch first — unless the user explicitly asked to commit to main and the server permits direct pushes. A user request does not bypass protected-branch rules; when the remote rejects direct updates, use the repository's required pull-request path. Do not ask the user whether to create a branch; just proceed with branch creation. The create-branch skill will still propose a branch name for the user to confirm.
Use the create-branch skill to create the branch. After create-branch completes, verify the current branch has changed before proceeding:
git branch --show-current
If still on main or master (e.g., the user aborted branch creation), stop — do not commit.
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 |
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 GH-1234
Fixes #1234
Fixes SENTRY-1234
Refs LINEAR-ABC-123
Fixescloses the issue when mergedRefslinks 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:
Co-Authored-By: Claude <noreply@anthropic.com>
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.
Examples
Simple fix
fix(api): Handle null response in user endpoint
The user API could return null for deleted accounts, causing a crash
in the dashboard. Add null check before accessing user properties.
Fixes SENTRY-5678
Co-Authored-By: Claude <noreply@anthropic.com>
Feature with scope
feat(alerts): Add Slack thread replies for alert updates
When an alert is updated or resolved, post a reply to the original
Slack thread instead of creating a new message. This keeps related
notifications grouped together.
Refs GH-1234
Refactor
ref: Extract common validation logic to shared module
Move duplicate validation code from three endpoints into a shared
validator class. No behavior change.
Breaking change
feat(api)!: Remove deprecated v1 endpoints
Remove all v1 API endpoints that were deprecated in version 23.1.
Clients should migrate to v2 endpoints.
BREAKING CHANGE: v1 endpoints no longer available
Fixes SENTRY-9999
Revert Format
revert: feat(api): Add new endpoint
This reverts commit abc123def456.
Reason: Caused performance regression in production.
Principles
- Each commit should be a single, stable change
- Commits should be independently reviewable
- The repository should be in a working state after each commit
References
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Direct-to-main instructions remain subordinate to server-side branch protection and required checks.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Frequently asked questions about Sentry Commit Messages
Similar skills
Release Candidate Preparation
Streamline your OpenAI Agents release process.
Gitmoji
Generate expressive commit messages with emojis.
GitHub Release
Automate your GitHub library release process effortlessly.
Commit Message Storyteller
Generate meaningful commit messages from your git diffs.
Author Contributions
Trace author contributions across branches in Git.
Implementation Kickoff
Streamline your code implementation process with ease.