What does the Sentry Commit Messages skill do?

It enforces Sentry-style commit conventions by checking branch safety, preventing direct commits to main/master, and generating properly formatted commit messages with conventional commit structure, issue references, and consistent formatting for headers, bodies, and footers.

What commit types does this skill support?

The skill supports these commit types: feat, fix, ref, perf, docs, test, build, ci, chore, style, meta, and license.

How should issue references be formatted in commit footers?

Use `Fixes GH-1234`, `Fixes #1234`, or `Fixes SENTRY-1234` to close an issue, or `Refs LINEAR-ABC-123` to link without closing. If changes were generated by a coding agent, include `Co-Authored-By: Claude ` as the only permitted AI-involvement marker.

What happens if I try to commit directly to main or master?

The skill checks the current branch and, if you're on main or master and haven't explicitly asked to commit there, it creates a feature branch using the create-branch skill and verifies the branch changed before proceeding; it stops without committing if still on main or master.

Skill

Generate Sentry-Formatted Git Commit Messages

Name: Sentry Commit Messages
Availability: OnlineOnly
Author: Antigravity

Sentry-style commit message skill enforcing conventional commit format, branch safety, and issue-reference footers.

Get skill

Works with github

Antigravity

Own this? Claim it

Spark score

out of 100

Updated 5 months ago

Version 1.0.0

Models

claude

Add to Favorites

Why it matters

Automate the creation of well-formatted Git commit messages adhering to Sentry's conventions, ensuring consistency and clarity in your codebase's history.

Outcomes

What it gets done

Enforce Sentry commit message format (type, scope, subject, body, footer).

Incorporate conventional commit types (feat, fix, ref, etc.).

Add issue references (GH-1234, SENTRY-1234) to commit footers.

Ensure branch safety by checking current branch before committing.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-commit | bash

Overview

Sentry Commit Messages

A Sentry-convention commit message skill enforcing conventional commit format, pre-commit branch safety, and correct issue-reference footers. Use whenever committing code or preparing a commit message where Sentry-style conventional formatting and branch safety are expected.

What it does

Sentry Commit Messages is a skill for writing Sentry-convention commits and enforcing branch safety before committing. It checks the current branch (git branch --show-current) and, if on main or master, requires creating a feature branch first via the create-branch skill - proceeding automatically rather than asking the user, then re-verifying the branch actually changed before allowing the commit to continue. A user's request to commit does not override protected-branch rules; if the remote rejects direct pushes, the required pull-request path must be used instead.

When to use - and when NOT to

Use it whenever the user asks to commit code, prepare a commit message, or save git changes, and Sentry-style conventional-commit formatting with issue references is expected. Commits follow a fixed structure:

<type>(<scope>): <subject>

<body>

<footer>

with the header required, scope optional, and every line under 100 characters. Twelve commit types are defined: feat, fix, ref (refactor, no behavior change), perf, docs, test, build, ci, chore, style, meta, and license.

Inputs and outputs

The subject line must be imperative present tense ("Add feature", not "Added feature"), capitalized, under 70 characters, with no trailing period. The body explains what and why rather than how, in imperative present tense, including motivation and contrast with prior behavior where relevant. The footer references issues with Fixes GH-1234, Fixes #1234, Fixes SENTRY-1234, or Refs LINEAR-ABC-123 - Fixes closes the issue on merge, Refs only links it. Breaking changes use a ! after the type/scope (feat(api)!:) plus a BREAKING CHANGE: footer line, and reverts use a dedicated revert: <original subject> format with a reason.

Integrations

When a change was primarily generated by a coding agent, the commit footer must include Co-Authored-By: Claude <noreply@anthropic.com> - this is explicitly the only AI-involvement indicator permitted; phrases like "Generated by AI" or "Written with Claude" anywhere else in the message are disallowed. Worked examples cover the range: a simple fix(api) commit with a Fixes SENTRY-5678 footer and Claude co-authorship, a feat(alerts) commit with a Refs GH-1234 footer, a plain ref: refactor commit with no scope, and a breaking-change example (feat(api)!: with a BREAKING CHANGE: footer line describing removed v1 endpoints). Underlying principles: each commit is a single, stable, independently reviewable change, and the repository must be in a working state after every commit.

Who it's for

Developers and coding agents committing to Sentry (or Sentry-convention) repositories who need consistent, well-formatted commits with correct issue linkage and safe branch handling rather than ad hoc commit messages or accidental direct commits to main.

FAQ

Common questions

Discussion