Commit — Agent Skill by Sentry

From the author

Use for every request to commit changes or draft a commit message. Creates Sentry-style conventional commits with issue references.

— the description by Sentry

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The commit skill provides a structured approach to version control by enforcing Sentry-style conventional commit messages. It guides users through branch verification, message formatting, and the inclusion of issue references, ensuring that repository history remains clean, readable, and programmatically useful.

What it does

Verifies the current branch to prevent direct commits to main or master.
Enforces the conventional commit format including type, scope, and subject.
Provides guidelines for writing clear, imperative commit subjects and bodies.
Supports the inclusion of issue references via Fixes or Refs footers.
Ensures breaking changes are clearly marked with the appropriate syntax.
Standardizes the use of git commit commands with multiple message arguments.

When to use it

When you need to draft a commit message for a set of changes.
When you want to ensure your commit history follows a consistent, professional standard.
When you need to link your code changes to specific issue tracking tickets.
When you are preparing to commit a breaking change that requires documentation.

Advantages

Promotes a clean and searchable project history.
Automates the inclusion of issue tracking links.
Reduces ambiguity in commit messages by enforcing imperative, present-tense language.
Prevents accidental commits to protected branches like main or master.

Usage examples

“Draft a commit message for fixing a null response in the user API, referencing SENTRY-5678.”: Generates a command: git commit -m "fix(api): Handle null response in user endpoint" -m "Return 404 when the user API finds a deleted account." -m "Fixes SENTRY-5678"

Install

Download the skill as a ZIP:
https://autogineer.com/agent-skills/getsentry/commit/download
Unzip it into the cross-client skills folder of your project:
```
mkdir -p .agents/skills && unzip commit.zip -d .agents/skills
```

Documentation by Sentry

Sentry Commit Messages

Before Committing

git branch --show-current

If the branch is main or master, create a feature branch unless the user explicitly requested a direct commit. Re-check the branch and stop if it is still main or master.

Commit one coherent, independently reviewable change at a time.

Message Rules

Use:

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

<optional body>

<optional footer>

Scope is optional. Add ! before : for a breaking change.
Write the subject in imperative, present tense; capitalize it, omit the trailing period, and keep it at 70 characters or fewer.
Keep every line under 100 characters.
Use the body only when useful. Explain what changed and why, including previous behavior or motivation when it helps.
Never include customer or organization names, user emails, support ticket contents, secrets, or PII. Describe the technical symptom instead.

Allowed types: feat, fix, ref, perf, docs, test, build, ci, chore, style, meta, license, and revert.

Use ref for refactoring without behavior changes, style for formatting without logic changes, and meta for repository metadata.

Footers

Fixes <issue> closes an issue when merged.
Refs <issue> links an issue without closing it.
For breaking changes, add BREAKING CHANGE: <impact>.

Creating the Commit

Use separate -m arguments for paragraphs and footers. Never put literal \n sequences in a commit message or open an interactive editor.

git commit -m "fix(api): Handle null response in user endpoint" \
  -m "Return 404 when the user API finds a deleted account." \
  -m "Fixes SENTRY-5678"

Files

ATTRIBUTION.mdAdded by AutoGineer836 B
LICENSELicence file added by AutoGineer10.5 KiB
SKILL.md1.8 KiB

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs a command-line tool

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Git Guardrails Claude Code
Matt Pocock· Community
Implement safety guardrails for Claude Code to prevent accidental execution of destructive Git commands.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskHas scriptsGitHub stars of the source repository317.5k
Setup Pre Commit
Matt Pocock· Community
Automates the configuration of Husky pre-commit hooks, lint-staged, and Prettier for your project.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository317.5k
CI CD And Automation
Addy Osmani· Community
A comprehensive framework for establishing automated CI/CD pipelines, quality gates, and deployment strategies.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository113.9k
Git Workflow And Versioning
Addy Osmani· Community
A comprehensive framework for disciplined Git workflows, atomic commits, and semantic versioning to ensure manageable and reliable code history.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository113.9k
Git Advanced Workflows
Seth Hobson· Community
Master advanced Git techniques for history management, bug isolation, and recovery.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k
Github Actions Templates
Seth Hobson· Community
A collection of production-ready GitHub Actions workflow templates for CI/CD automation.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskGitHub stars of the source repository42.3k