commit

tarafından sentry

We need to translate the given English text into Turkish, preserving the name "commit" if it appears. The text describes a skill that enforces Sentry conventional commit format. We must not add any extra commentary, labels, or formatting. Just the translation. The text: "Enforces Sentry conventional commit format with proper types, scopes, and issue references. Requires feature branch creation before committing to main or master; uses the create-branch skill to manage branch workflow Supports 12 commit types (feat, fix, ref, perf, docs, test, build, ci, chore, style, meta, license) with clear subject line rules and footer patterns for issue references Includes Co-Authored-By attribution for AI-generated changes and handles breaking changes with explicit..." Note: The text ends with "explicit..." possibly incomplete. We'll translate as is. Translation: "Sentry geleneksel commit formatını uygun türler, kapsamlar ve sorun referansları ile zorunlu kılar. Ana veya master dalına

npx skills add https://github.com/getsentry/skills --skill commit

ZIP İndir GitHub

896

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"