Commit

Enforces Sentry's conventional commit format and stops you from accidentally committing to main. It checks your current branch first, auto-creates a feature branch if needed, then walks you through structured commit messages with proper type prefixes, scopes, and issue references. The AI attribution handling is smart: it adds a Co-Authored-By line for Claude but nothing else, no "AI generated" noise in your git history. Useful if you're working in a Sentry codebase or just want disciplined commit hygiene without thinking about it. The branch protection alone makes it worth using since it won't let you footgun yourself on protected branches.

skills.sh installs: 359
GitHub stars: 39.4K
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add sickn33/antigravity-awesome-skills --skill commit --agent claude-code

Installs into .claude/skills of the current project.

Files

Sentry Commit Messages

Follow these conventions when creating commits for Sentry projects.

When to Use

The user asks to commit code, prepare a commit message, or save changes in git.
You need Sentry-style commit formatting with conventional commit structure and issue references.
The task requires enforcing branch safety before committing, especially avoiding direct commits on main or master.

Prerequisites

Before committing, always check the current branch:

git branch --show-current

Read repository policy before creating a commit. If the default branch is PR-only, create an authorized topic branch and use the repository's native maintainer flow, even when an administrator could bypass server checks. AAS requires antigravity-maintainer-batch-release and protected source PRs.

SKILL.md on GitHub

Sponsors

Promote your product hereReach 125k+ visitors monthly Promote your product hereReach 125k+ visitors monthly