commit

Solid

ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.

Code & Development 39,350 stars 6386 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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: ```bash git branch --show-current ``` **If you're on `main` or `master`, you MUST create a feature branch first** — unless the user explicitly asked to commit to main. Do not ask the user whether to create a branch; just proceed with branch creation. The `create-branch` skill will still propose a branch name for the user to confirm. Use the `create-branch` skill to create the branch. After `create-branch` completes, verify the current branch has changed before proceeding: ```bash git branch --show-current ``` If still on `main` or `master` (e.g., the user aborted branch creation), stop — do not commit. ## Format ``` <type>(<scope>): <subject> <body> <footer> ``` The header is required. Scope is optional. All lines must stay under 100 characters. ## Commit Types | Type | Purpose | |------|---------| | `feat` | New feature | | `fix` | Bug fix | | `ref` | Refactoring (no behavior change) | | `perf` | Performance improvement | | `docs` | Documentation only | | `test` | Test additions or correc...

Details

Author
sickn33
Repository
sickn33/antigravity-awesome-skills
Created
4 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

commit

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.

27,705 Updated today
davila7
Code & Development Listed

commit

Handles git commits with concise, list-style messages and no co-author trailers. Use this skill whenever the user asks to commit, says "commit", "/commit", "commit this", "save my changes", or any variation of requesting a git commit. This skill MUST be used for every commit operation — it overrides the default commit behavior.

0 Updated 2 days ago
Stoica-Mihai
Code & Development Listed

ape-commit

Defines how to write and format git commit messages. Use this skill whenever the user asks you to write, draft, suggest, or format a git commit message, summarize changes into a commit, or help stage and describe code changes. Trigger even for casual requests like "write me a commit for this" or "what should my commit say".

12 Updated 3 days ago
arpitbbhayani
Code & Development Listed

conventional-commits

Enforces Conventional Commits format for git commit messages. Use when formatting commits or validating message structures. For git commands, see git-control.

2 Updated 1 weeks ago
tuliosousapro
Code & Development Listed

commit-messages

Generate clear, conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or preparing releases.

0 Updated today
israel7852