explainx.ainewsletter3.02k
Productivity

commit▌

sickn33/antigravity-awesome-skills · updated Apr 8, 2026

$npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill commit
0 commentsdiscussion
summary

Follow these conventions when creating commits for Sentry projects.

skill.md

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

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:

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 corrections
build Build system or dependencies
ci CI configuration
chore Maintenance tasks
style Code formatting (no logic change)
meta Repository metadata
license License changes

Subject Line Rules

  • Use imperative, present tense: "Add feature" not "Added feature"
  • Capitalize the first letter
  • No period at the end
  • Maximum 70 characters

Body Guidelines

  • Explain what and why, not how
  • Use imperative mood and present tense
  • Include motivation for the change
  • Contrast with previous behavior when relevant

Footer: Issue References

Reference issues in the footer using these patterns:

Fixes GH-1234
Fixes #1234
Fixes SENTRY-1234
Refs LINEAR-ABC-123
  • Fixes closes the issue when merged
  • Refs links without closing

AI-Generated Changes

When changes were primarily generated by a coding agent (like Claude Code), include the Co-Authored-By attribution in the commit footer:

Co-Authored-By: Claude <noreply@anthropic.com>

This is the only indicator of AI involvement that should appear in commits. Do not add phrases like "Generated by AI", "Written with Claude", or similar markers in the subject, body, or anywhere else in the commit message.

Examples

Simple fix

fix(api): Handle null response in user endpoint

The user API could return null for deleted accounts, causing a crash
in the dashboard. Add null check before accessing user properties.

Fixes SENTRY-5678
Co-Authored-By: Claude <noreply@anthropic.com>

Feature with scope

feat(alerts): Add Slack thread replies for alert updates

When an alert is updated or resolved, post a reply to the original
Slack thread instead of creating a new message. This keeps related
notifications grouped together.

Refs GH-1234

Refactor

ref: Extract common validation logic to shared module

Move duplicate validation code from three endpoints into a shared
validator class. No behavior change.

Breaking change

feat(api)!: Remove deprecated v1 endpoints

Remove all v1 API endpoints that were deprecated in version 23.1.
Clients should migrate to v2 endpoints.

BREAKING CHANGE: v1 endpoints no longer available
Fixes SENTRY-9999

Revert Format

revert: feat(api): Add new endpoint

This reverts commit abc123def456.

Reason: Caused performance regression in production.

Principles

  • Each commit should be a single, stable change
  • Commits should be independently reviewable
  • The repository should be in a working state after each commit

References

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.5★★★★★64 reviews
  • ★★★★★Advait Verma· Dec 28, 2024

    Solid pick for teams standardizing on skills: commit is focused, and the summary matches what you get after install.

  • ★★★★★Advait Tandon· Dec 24, 2024

    Useful defaults in commit — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Mia Khanna· Dec 16, 2024

    We added commit from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Emma Mensah· Dec 12, 2024

    commit has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • ★★★★★Emma Diallo· Dec 12, 2024

    I recommend commit for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • ★★★★★Hana Jain· Dec 4, 2024

    commit is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • ★★★★★Naina Huang· Nov 23, 2024

    commit reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • ★★★★★Lucas Mensah· Nov 19, 2024

    We added commit from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Naina Choi· Nov 15, 2024

    I recommend commit for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • ★★★★★Henry Gupta· Nov 7, 2024

    Solid pick for teams standardizing on skills: commit is focused, and the summary matches what you get after install.

showing 1-10 of 64

1 / 7