Commit

by davila78da17d671b6fNo license32K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

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.

Instructions onlySoftware Development
AI-generated overview

Formats Git commit messages using Sentry's conventional-commit conventions, including issue references.

What it does
Provides Sentry's commit message conventions: header format with type and optional scope, a table of allowed commit types, subject line rules, body guidelines, and footer issue-reference patterns. It also supplies worked examples for simple fixes, scoped features, refactors, breaking changes, and reverts. The output is a formatted commit message rather than any code change.
When to use it
Use when writing or reviewing commit messages for Sentry projects, or when formatting git history to match these conventions. It suits commits that need correct type prefixes, imperative subjects, and issue references such as Fixes or Refs.
Requirements
No tools, packages, or credentials; it is instructions only and ships no scripts.

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

TypePurpose
featNew feature
fixBug fix
refRefactoring (no behavior change)
perfPerformance improvement
docsDocumentation only
testTest additions or corrections
buildBuild system or dependencies
ciCI configuration
choreMaintenance tasks
styleCode formatting (no logic change)
metaRepository metadata
licenseLicense 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-1234Fixes #1234Fixes SENTRY-1234Refs LINEAR-ABC-123
  • Fixes closes the issue when merged
  • Refs links without closing

Examples

Simple fix

fix(api): Handle null response in user endpoint
The user API could return null for deleted accounts, causing a crashin the dashboard. Add null check before accessing user properties.
Fixes SENTRY-5678

Feature with scope

feat(alerts): Add Slack thread replies for alert updates
When an alert is updated or resolved, post a reply to the originalSlack thread instead of creating a new message. This keeps relatednotifications grouped together.
Refs GH-1234

Refactor

ref: Extract common validation logic to shared module
Move duplicate validation code from three endpoints into a sharedvalidator 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 availableFixes 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

Source and attribution

Source:davila7/claude-code-templatesincli-tool/components/skills/sentry/commitat commit8da17d6

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from davila7/claude-code-templates

React Best Practices

davila7

A React and Next.js performance guide with 40+ rules on waterfalls, bundles, rendering and re-renders.

Includes scripts
Software Development32Kupdated today

Web Performance Optimization

davila7

Guides developers through measuring and fixing web performance issues such as Core Web Vitals, bundle size, images and caching.

Software Development32Kupdated today

Find Bugs

davila7

Reviews local branch changes for bugs, security vulnerabilities, and code quality issues, reporting findings without making changes.

Security32Kupdated today

Browser Automation

davila7

Guides browser automation with Playwright and Puppeteer for testing, scraping, and agentic browser control.

Software Development32Kupdated today

Code Review

davila7

Guides code reviews of pull requests using Sentry engineering practices, covering security, performance, testing and design.

Software Development32Kupdated today

Scikit Learn

davila7

Guides classical machine learning in Python with scikit-learn, covering preprocessing, model training, evaluation and pipelines.

Includes scripts
Data & Analytics32Kupdated today

More in Software Development

Playground

anthropics

Featured

Builds self-contained interactive HTML playgrounds with controls, live preview, and copyable prompt output.

Software Development37Kupdated today

M5 Onboard

anthropics

Featured

Provisions M5Stack ESP32 boards by detecting them on USB, flashing UIFlow 2.0 firmware, and installing a MicroPython app bundle.

Software Development37Kupdated today

Cardputer Buddy

anthropics

Featured

Guides iterating on a Cardputer-Adv MicroPython app bundle: adding apps, pushing files over USB-serial, tailing logs, and running REPL commands.

Software Development37Kupdated today

Web Design Guidelines

vercel-labs

Featured

Reviews UI code against Web Interface Guidelines fetched from a remote source and reports findings as file:line entries.

Software Development32Kupdated 5 weeks ago

Vercel React Native Skills

vercel-labs

Featured

React Native and Expo best-practice rules covering list performance, animation, navigation, UI patterns, state, and monorepo setup.

Software Development32Kupdated 5 weeks ago

Vercel React Best Practices

vercel-labs

Featured

Vercel's React and Next.js performance guidelines, organized as 70 rules for writing, reviewing, and refactoring code.

Software Development32Kupdated 5 weeks ago