Percerno Skillsbeta
← everything it can do · other

Commit TEXT

Generates and executes git commits using Sentry-style conventional commit messages, including issue references and breaking change indicators. It ensures proper branch handling and formats messages with specific type, scope, and footer conventions.

2 uses this weeksource getsentrylicence Apache-2.0
Quality gate: PASS · better answers · measured 2026-10-23
Blind-judged against the bare model on 2 requests: average lift +3.5 points (specificity, structure, method, fit).
won 2/2, lift +3.5, tokens ×30.4
Security scan: clean · 2026-10-24 · 1 files · ran in sandbox
no network calls, shell tricks, credential access or instruction tampering found in its files.

Try asking

Say it in your own words; the assistant finds this recipe by itself. Examples:

“Commit ændringerne i auth-mappen og link dem til JIRA-123.”
“Jeg har rettet null pointer exception i betalingsgatewayen. Skriv en commit message til det.”
“git commit de nuværende filer med en bemærkning om breaking change vedrørende API v2.”
“Commit the changes in the auth module and link it to JIRA-123.”
“I fixed the null pointer exception in the payment gateway. Please write a commit message for this.”
“git commit the current staged files with a breaking change note about the API v2 migration.”
Try this skill from Claude, ChatGPT or a chat on your own page. Free plan, no credit card.Get started free

Good for

gitcommitconventional-commitssentryversion-controlissue-trackingrefactoringbug-fix

Not for

Do not use this skill for creating pull requests, pushing to remote repositories, or resolving merge conflicts. It is not for general git history manipulation like rebasing or cherry-picking, nor for initializing new repositories.

Details

When it is the right choice

Use this skill when the user asks to commit staged changes, draft a commit message, or finalize a specific code change. It is appropriate for any request involving `git commit` where adherence to Sentry's specific message format and issue linking requirements is needed.

The full recipe the assistant reads

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"
Files in this skill (2)
  • LICENSE
  • SKILL.md
Where it comes from

Vendored from getsentry/skills, commit f57ada2d0b64, path skills/commit, licence Apache-2.0. The upstream licence file ships inside the skill.