commit
Create Sentry-Compliant Commits
Also available from: DavidOpDeBeeck,getsentry,davila7,0xmsc,Codename-11,0xmsc
Generate professional commit messages that follow Sentry engineering standards and integrate with their issue tracking system.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "commit". Add new Slack integration for alert notifications
Expected outcome:
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
Using "commit". Fix null error in user API
Expected outcome:
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>
Security Audit
SafeThis skill is pure documentation providing commit message guidelines. Static analysis flagged external_commands, network URLs, and cryptographic patterns, but evaluation confirms these are false positives. The file contains only documentation examples of git commands and reference URLs - no executable code or actual network requests.
Quality Score
What You Can Build
Sentry Developer Workflow
Create properly formatted commits that automatically link to Sentry issues when merged
AI Code Review Attribution
Add proper AI contributor attribution following best practices
Team Convention Enforcement
Maintain consistent commit history across team repositories
Try These Prompts
Create a commit message for adding a new user authentication feature. Reference the Sentry issue SENTRY-1234.
Write a commit message for fixing a null pointer error in the API endpoint. Include issue reference GH-5678.
Create a commit message for refactoring validation logic. Mark it as AI-generated with Claude attribution.
Write a commit message for removing deprecated API endpoints. Document the breaking change properly.
Best Practices
- Always include an issue reference in the footer to link commits to tracking systems
- Use imperative mood in subject lines (Add, Fix, Remove not Added, Fixed, Removed)
- Keep subject lines under 70 characters for optimal display in git tools
Avoid
- Do not use past tense in commit subjects (should be 'Add feature' not 'Added feature')
- Avoid generic messages like 'fix bug' or 'update code' without specifics
- Do not include AI disclosure phrases in subject or body - only use Co-Authored-By footer