skilld
All skills
getsentry avatar

/commit

@412f236 official
by Sentrygetsentry/skills1k stars
53

Use for every request to commit changes or draft a commit message. Creates Sentry-style conventional commits with issue references.

Ask your Agent

Use this Skill: https://skilld.dev/gh/getsentry/skills/commit

This session only. Nothing lands on disk.

SKILL.md

≈35 tokens always: the name and description. ≈425 when used: this file.

Sentry Commit Messages

Before Committing

git branch --show-current

If the branch is main or master, create a feature branch unless the user explicitly requested a direct commit. Re-check the branch and stop if it is still main or master.

Commit one coherent, independently reviewable change at a time.

Message Rules

Use:

<type>(<scope>): <subject>

<optional body>

<optional footer>
  • Scope is optional. Add ! before : for a breaking change.
  • Write the subject in imperative, present tense; capitalize it, omit the trailing period, and keep it at 70 characters or fewer.
  • Keep every line under 100 characters.
  • Use the body only when useful. Explain what changed and why, including previous behavior or motivation when it helps.
  • Never include customer or organization names, user emails, support ticket contents, secrets, or PII. Describe the technical symptom instead.

Allowed types: feat, fix, ref, perf, docs, test, build, ci, chore, style, meta, license, and revert.

Use ref for refactoring without behavior changes, style for formatting without logic changes, and meta for repository metadata.

Footers

  • Fixes <issue> closes an issue when merged.
  • Refs <issue> links an issue without closing it.
  • For breaking changes, add BREAKING CHANGE: <impact>.

Creating the Commit

Use separate -m arguments for paragraphs and footers. Never put literal \n sequences in a commit message or open an interactive editor.

git commit -m "fix(api): Handle null response in user endpoint" \
  -m "Return 404 when the user API finds a deleted account." \
  -m "Fixes SENTRY-5678"

Source: SKILL.md on GitHub

Third-party checks

No alerts16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill provides guidelines and safe Git commands for creating standardized Sentry-style commit messages. It includes explicit instructions to avoid committing sensitive data like PII or secrets.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer6mo

    1 file scanned · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 412f236. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 months ago

Topics

  • Git/VCS
  • conventional-commits
  • commit-messages
  • sentry
  • branch-management
  • issue-references

README badge

README badge for getsentry/skills/commit

What it does

Generates commits following Sentry's conventional commit format, with required scope notation, issue references, and AI attribution. Enforces branch protection (prevents commits to main/master), validates subject line length and imperative mood, and prevents customer PII in commit bodies.

Generated from the current SKILL.md.

Frequently asked

Should I always use this skill when committing?
Yes. The skill description states to always use it when committing code changes and never commit directly without it.
What happens if I'm on the main or master branch?
You must create a feature branch first before committing, unless explicitly asked to commit to main. The skill will not allow commits directly to main or master.
Do I need to include a scope in the commit format?
No. The scope is optional. Only the type and subject are required; the format is `<type>(<scope>): <subject>` where scope can be omitted.
How should I reference issues in commit messages?
Use `Fixes GH-1234`, `Fixes #1234`, `Fixes SENTRY-1234` to close an issue, or `Refs LINEAR-ABC-123` to link without closing.
Should I add AI attribution to commits?
Yes. Include `Co-Authored-By: (agent name and attribution byline)` in the footer when changes were primarily generated by a coding agent. This is the only indicator of AI involvement that should appear.

Generated from the current SKILL.md. These answers refresh after source changes.