Open Skills Logo
Open Skills

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.

Author

@sickn33

Category

Development Tools

Install

Hot:0

Download and extract to your skills directory

Copy command and send to OpenClaw for auto-install:

Download and install this skill https://openskills.cc/api/download?slug=sickn33-skills-commit&locale=en&source=copy

Sentry Commit Message Guidelines

Overview


Write git commit messages following Sentry's conventions; supports the Conventional Commits format and Sentry issue references.

Use Cases


  • When committing code changes: Write commit messages in the standard format to ensure a clear and consistent history for the team.

  • Linking Sentry issues: Reference SENTRY, GitHub, or Linear issues in the commit footer to automatically close or associate tickets.

  • AI-assisted development: When code is generated using AI tools like Claude Code, properly add a Co-Authored-By declaration.

    • Core Features


  • Standardized commit format: Provide a unified <type>(<scope>): <subject> format, supporting 12 commit types (feat, fix, ref, perf, docs, test, build, ci, chore, style, meta, license).

  • Sentry issue references: Associate tracking systems like SENTRY-xxxx, GH-xxxx, LINEAR-xxx using the Fixes or Refs keywords.

  • Breaking change marking: Use the ! token or a BREAKING CHANGE footer to clearly denote incompatible API changes.

    • Frequently Asked Questions

    What are the rules for the commit subject?


    Use the imperative present tense ("Add" instead of "Added"), capitalize the first letter, do not end with a period, and keep it to a maximum of 70 characters.

    What's the difference between commit types like feat, fix, ref, etc.?


  • feat: new feature

  • fix: bug fix

  • ref: refactor (no behavior change)

  • perf: performance improvement

  • docs: documentation-only changes

  • test: testing-related

  • Other types include build, ci, chore, style, meta, license

    • How should AI-generated code be committed?


    Add Co-Authored-By: Claude <noreply@anthropic.com> to the commit footer; do not use phrases like "Generated by AI" in the subject or body.