commit
We need to translate the given English text into Hindi. The text describes a skill that enforces Sentry conventional commit format. We must preserve product names, protocol names, URLs, numbers, technical terms. The name "commit" is to be preserved if it appears in the source text. The source text does not contain the word "commit" as a standalone name? Actually it says "Enforces Sentry conventional commit format" - "commit" is part of "conventional commit format". But the instruction says "Name to preserve: commit". So we should preserve the word "commit" as is. Also "Sentry" is a product name, preserve. "create-branch" is a skill name, preserve. Numbers like 12, types like feat, fix, etc. preserve. Also "Co-Authored-By" preserve. "AI-generated" preserve? It's a term, but we can translate? The instruction says preserve technical terms. "AI-generated" might be considered technical, but it's common. Better to preserve as is or translate? The instruction says
npx skills add https://github.com/getsentry/skills --skill commitSentry 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"