commit
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.
IT & Software DevelopmentProject & Program ManagementOperations & Supply ChainAI & Automation
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
mainormaster.
Prerequisites
Before committing, always check the current branch:
git branch --show-currentIf you're on main or master, you MUST create a feature branch first — unless the user explicitly asked to commit to main and the server permits direct pushes. A user request does not bypass protected-branch rules; when the remote rejects direct updates, use the repository's required pull-request path. 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:
git branch --show-currentIf 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 m
Subscribers only
The full skill, its 1 bundled files and every download is included with every paid Complete AI plan.
Details
| Source | community |
|---|---|
| License | — |
| Risk label | critical ("critical" means the skill may run commands or touch files — read before use) |
| Files | SKILL.md |
| Added | 2026-09-04 |
Related skills
acceptance-orchestrator
Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
ai-loop
Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.
airflow-dag-patterns
Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.
antigravity-workflows
Use when asked to ship a SaaS MVP, audit application security, build an AI agent, run browser QA, or design a domain model with multiple skills and verified checkpoints.
ask-questions-if-underspecified
Clarify requirements before implementing. Use when serious doubts arise.