跳到主要内容
知知仓学习社ZHICANG

commit

ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conv…

不碰外部（只输出文字）无严重或高危命中sickn33/agentic-awesome-skills

它会碰到什么

扫了多少1 个文本文件，5 KB
它会碰到什么不碰外部（只输出文字）
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0

这一栏是扫描器报的事实，不是结论。命中多不等于有毒（安全工具、规则库、示例脚本本来就会包含危险写法），命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系，需要你自己看。

技能内容

Sentry Commit Messages

Follow these conventions when creating commits for Sentry projects.

When to Use

  • The user asks to commit code, prepare a commit message, or save changes in git.
  • You need Sentry-style commit formatting with conventional commit structure and issue references.
  • The task requires enforcing branch safety before committing, especially avoiding direct commits on main or master.

Prerequisites

Before committing, always check the current branch:

git branch --show-current

If you're on main or master, you MUST create a feature branch first — unless the user explicitly asked to commit to main and the server permits direct pushes. A user request does not bypass protected-branch rules; when the remote rejects direct updates, use the repository's required pull-request path. Do not ask the user whether to create a branch; just proceed with branch creation. The create-branch skill will still propose a branch name for the user to confirm.

Use the create-branch skill to create the branch. After create-branch completes, verify the current branch has changed before proceeding:

git branch --show-current

If still on main or master (e.g., the user aborted branch creation), stop — do not commit.

Format

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

<body>

<footer>

The header is required. Scope is optional. All lines must stay under 100 characters.

Commit Types

| Type | Purpose |

|------|---------|

| feat | New feature |

| fix | Bug fix |

| ref | Refactoring (no behavior change) |

| perf | Performance improvement |

| docs | Documentation only |

| test | Test additions or corrections |

| build | Build system or dependencies |

| ci | CI configuration |

| chore | Maintenance tasks |

| style | Code formatting (no logic change) |

| meta | Repository metadata |

| license | License changes |

Subject Line Rules

  • Use imperative, present tense: "Add feature" not "Added feature"
  • Capitalize the first letter
  • No period at the end
  • Maximum 70 characters

Body Guidelines

  • Explain what and why, not how
  • Use imperative mood and present tense
  • Include motivation for the change
  • Contrast with previous behavior when relevant

Footer: Issue References

Reference issues in the footer using these patterns:

Fixes GH-1234
Fixes #1234
Fixes SENTRY-1234
Refs LINEAR-ABC-123
  • Fixes closes the issue when merged
  • Refs links without closing

AI-Generated Changes

When changes were primarily generated by a coding agent (like Claude Code), include the Co-Authored-By attribution in the commit footer:

Co-Authored-By: Claude <noreply@anthropic.com>

This is the only indicator of AI involvement that should appear in commits. Do not add phrases like "Generated by AI", "Written with Claude", or similar markers in the subject, body, or anywhere else in the commit message.

Examples

Simple fix

fix(api): Handle null response in user endpoint

The user API could return null for deleted accounts, causing a crash
in the dashboard. Add null check before accessing user properties.

Fixes SENTRY-5678
Co-Authored-By: Claude <noreply@anthropic.com>

Feature with scope

feat(alerts): Add Slack thread replies for alert updates

When an alert is updated or resolved, post a reply to the original
Slack thread instead of creating a new message. This keeps related
notifications grouped together.

Refs GH-1234

Refactor

ref: Extract common validation logic to shared module

Move duplicate validation code from three endpoints into a shared
validator class. No behavior change.

Breaking change

feat(api)!: Remove deprecated v1 endpoints

Remove all v1 API endpoints that were deprecated in version 23.1.
Clients should migrate to v2 endpoints.

BREAKING CHANGE: v1 endpoints no longer available
Fixes SENTRY-9999

Revert Format

revert: feat(api): Add new endpoint

This reverts commit abc123def456.

Reason: Caused performance regression in production.

Principles

  • Each commit should be a single, stable change
  • Commits should be independently reviewable
  • The repository should be in a working state after each commit

References

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Direct-to-main instructions remain subordinate to server-side branch protection and required checks.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

想直接用这个技能？

本站把开放许可（MIT / Apache 等）的技能按仓库打包整理到网盘，点一下转存到你自己的网盘，不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接，不打包。

去原始仓库

它属于哪个仓库

仓库sickn33/agentic-awesome-skills
星标★ 46,490
本站分层T1
该仓技能数6676
原文件路径plugins/agentic-awesome-skills/skills/commit/SKILL.md

同一个仓库里的其他技能

看这个仓库的全部 6676 个技能

同名技能的其他版本

有 4 个不同仓库或目录里都有叫 commit 的技能。它们内容并不相同，别混用：