git-commit-specification
Provides guidance on writing conventional commit messages and managing git submission workflows.
Install
mkdir -p .claude/skills/git-commit-specification && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5919" && unzip -o skill.zip -d .claude/skills/git-commit-specification && rm skill.zipInstalls to .claude/skills/git-commit-specification
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
编写 BK-CI Git 提交信息和整理提交边界时使用，例如选择 commit type、撰写 commit message、判断是否拆分提交和准备 PR 前自检。当用户要提交代码而不是讨论实现细节时优先使用。Key capabilities
- →Guides commit message formatting
- →Assists in categorizing changes as feat, fix, or refactor
- →Supports PR preparation and self-checks
How it works
It provides a framework for expressing intent in commit messages and ensuring logical separation of changes.
Inputs & outputs
When to use git-commit-specification
- →Formatting commit messages correctly
- →Preparing a PR for review
- →Structuring code changes into logical commits
About this skill
Git 提交规范
适用场景
- 编写 commit message
- 判断本次改动应归类为
feat、fix、refactor等哪一类 - 整理提交边界，避免一个提交塞入多类无关改动
- 提交前做最基本的自检
不适用场景
- 讨论具体业务实现方案
- 修改 Git 历史或做高风险 Git 操作
- 只是创建分支，但不涉及提交规范本身
快速指导
- 这个 skill 关注的是“提交如何表达改动意图”，不是 Git 命令大全。
- commit message 优先表达改动性质和目的，常见类型包括：
feat：新增能力fix：修复问题refactor：重构但不改外部行为perf：性能优化test：测试补充或调整docs：文档变更chore：构建、配置、工具链维护
- 提交信息格式保持简洁稳定，例如：
feat: 添加流水线模板功能 #1234 - 一个提交只表达一类主要意图；如果混入多个独立目的，优先拆分提交。
- 提交前先做最小自检：改动范围是否聚焦、是否包含敏感信息、是否通过必要验证。
- 高风险历史整理操作不应作为默认建议写进主 skill；如确有需要，应按具体场景单独判断。
高信号规则
- commit message 的核心是让评审者快速理解“这次改动为什么存在”
- 类型选择要服务于改动意图，不要机械套用
- 提交边界清楚，比 message 写得花更重要
- Issue 编号、范围标记等信息应服从团队约定，但不要盖过主语义
关键陷阱
- 一个提交同时混入功能、重构、修复和格式化
- message 只写“update”或“fix bug”这类低信息描述
- 把交互式、破坏性或高风险 Git 操作当成默认规范
延伸阅读
- 如需准备 PR，可在当前改动基础上补充评审上下文和验证结果
- 如需处理高风险 Git 历史整理，按具体仓库流程单独判断，不在本 skill 中默认展开
When not to use it
- →When discussing specific business implementation schemes
- →When performing high-risk Git history modifications
Limitations
- →Does not handle high-risk Git history operations
- →Does not replace team-specific conventions
How it compares
It focuses on the intent and quality of commit messages rather than providing a general Git command reference.
Compared to similar skills
git-commit-specification side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| git-commit-specification (this skill) | 1 | 3mo | No flags | Beginner |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
| git-commits | 21 | 4mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by TencentBlueKing
View all by TencentBlueKing →You might also like
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
git-commits
bonny
Create well-structured git commits in logical chunks following best practices
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
github-multi-repo
ruvnet
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration
git-workflow-enforcer
CrazyDubya
Ensures commits follow conventional commits, branch naming conventions, and PR templates. Use when creating commits, branches, or PRs, or when user mentions git workflow.