commit
Enforces Sentry conventional commit format with proper types, scopes, and issue references.
- Requires feature branch creation before committing to main or master; uses the
create-branchskill to manage branch workflow - Supports 12 commit types (feat, fix, ref, perf, docs, test, build, ci, chore, style, meta, license) with clear subject line rules and footer patterns for issue references
- Includes Co-Authored-By attribution for AI-generated changes and handles breaking changes with explicit BREAKING CHANGE footer notation
- Enforces imperative present tense, 70-character subject limits, and real newlines in commit bodies to avoid malformed messages
Sentry Commit Messages
Follow these conventions when creating commits for Sentry projects.
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. Do not ask the user whether to create a branch; just proceed with branch creation, then re-check the current branch before committing. If still on main or master, stop — do not commit.
Format
<type>(<scope>): <subject>
More from getsentry/skills
security-review
Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.
5.3Kcode-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
4.4Kfind-bugs
Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.
2.4Kagents-md
Creates and maintains concise AGENTS.md and CLAUDE.md project instruction files. Use when asked to create AGENTS.md, update AGENTS.md, maintain agent docs, set up CLAUDE.md, document repository agent conventions, or keep coding-agent instructions minimal and reference-backed.
2.3Kcode-review
Perform code reviews following Sentry engineering practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.
2.2Kiterate-pr
Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.
1.9K