git-commit-specification
Original：🇨🇳 Chinese
Translated
Git Commit Specification, covering commit message format (feat/fix/refactor), Issue linking, branch naming, PR submission preparation, and rebase usage. Used when users submit code, write commit messages, create branches, or prepare PRs.
33installs
Sourcetencentblueking/bk-ci
Added on
NPX Install
npx skill4agent add tencentblueking/bk-ci git-commit-specificationTags
Translated version includes tags in frontmatterSKILL.md Content (Chinese)
View Translation Comparison →Git Commit Specification
Quick Reference
Format: Tag: Commit description #Issue number
Example: feat: Add pipeline template feature #1234
Branches: feature/xxx | bugfix/xxx | hotfix/xxxTag Types
| Tag | Description | Example |
|---|---|---|
| New feature | |
| Bug fix | |
| Code refactoring | |
| Performance optimization | |
| Testing | |
| Documentation | |
| Build/tooling | |
| Destructive deletion | |
When to Use
- Submit code
- Create a branch
- Prepare a PR
- Write commit messages
Commit Format
bash
# Standard format
feat: Add pipeline template feature #1234
# With scope
feat(process): Add pipeline template feature #1234Branch Naming
bash
feature/pipeline-template-support # Feature branch
bugfix/build-log-missing # Bug fix branch
hotfix/critical-security-issue # Hotfix branchPreparations Before PR Submission
bash
# Use rebase to streamline commits
git rebase -i HEAD~5
# Sync upstream code
git fetch upstream
git rebase upstream/developChecklist
Confirm before submitting code:
- commit message complies with format specifications
- Linked Issue number
- Used rebase to streamline commits
- No sensitive information included
- Code passed local tests