Git Commit 规范指南：使用 Conventional Commits 标准化提交信息

git-commit by github/awesome-copilot

18,400 周安装量

27,200 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/github/awesome-copilot --skill git-commit

开发开发运维生产力

🇨🇳中文介绍

使用 Conventional Commits 规范进行 Git 提交

概述

使用 Conventional Commits 规范创建标准化、语义化的 git 提交。分析实际的代码差异来确定合适的类型、作用域和提交信息。

Conventional Commits 格式

<类型>[可选作用域]: <描述>

[可选正文]

[可选脚注]

提交类型

类型	用途
`feat`	新功能
`fix`	错误修复
`docs`	仅文档更改
`style`	格式化/样式调整（不影响逻辑）

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

2. 暂存文件（如果需要）

如果未暂存任何文件，或者希望以不同方式分组更改：

# 暂存特定文件
git add path/to/file1 path/to/file2

# 按模式暂存
git add *.test.*
git add src/components/*

# 交互式暂存
git add -p

切勿提交机密信息（如 .env、credentials.json、私钥等）。

3. 生成提交信息

分析差异以确定：

类型：这是什么类型的更改？
作用域：哪个区域/模块受到影响？
描述：对更改内容的一行总结（使用现在时、祈使语气，少于72个字符）

# 单行提交
git commit -m "<类型>[作用域]: <描述>"

# 多行提交（包含正文/脚注）
git commit -m "$(cat <<'EOF'
<类型>[作用域]: <描述>

<可选正文>

<可选脚注>
EOF
)"

每次提交对应一个逻辑更改
使用现在时："add" 而非 "added"
使用祈使语气："fix bug" 而非 "fixes bug"
引用问题：Closes #123、Refs #456
保持描述少于72个字符

切勿更新 git 配置
未经明确请求，切勿运行破坏性命令（--force、硬重置）
除非用户要求，切勿跳过钩子（--no-verify）
切勿强制推送到 main/master 分支
如果提交因钩子失败，请修复问题并创建新的提交（不要修改原提交）

🇺🇸English

Git Commit with Conventional Commits

Overview

Create standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff to determine appropriate type, scope, and message.

Conventional Commit Format

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Commit Types

Type	Purpose
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation only
`style`	Formatting/style (no logic)
`refactor`	Code refactor (no feature/fix)
`perf`	Performance improvement
`test`	Add/update tests
`build`	Build system/dependencies
`ci`	CI/config changes
`chore`	Maintenance/misc
`revert`	Revert commit

Breaking Changes

# Exclamation mark after type/scope
feat!: remove deprecated endpoint

# BREAKING CHANGE footer
feat: allow config to extend other configs

BREAKING CHANGE: `extends` key behavior changed

Workflow

1. Analyze Diff

# If files are staged, use staged diff
git diff --staged

# If nothing staged, use working tree diff
git diff

# Also check status
git status --porcelain

2. Stage Files (if needed)

If nothing is staged or you want to group changes differently:

# Stage specific files
git add path/to/file1 path/to/file2

# Stage by pattern
git add *.test.*
git add src/components/*

# Interactive staging
git add -p

Never commit secrets (.env, credentials.json, private keys).

3. Generate Commit Message

Analyze the diff to determine:

Type : What kind of change is this?
Scope : What area/module is affected?
Description : One-line summary of what changed (present tense, imperative mood, <72 chars)

4. Execute Commit

# Single line
git commit -m "<type>[scope]: <description>"

# Multi-line with body/footer
git commit -m "$(cat <<'EOF'
<type>[scope]: <description>

<optional body>

<optional footer>
EOF
)"

Best Practices

One logical change per commit
Present tense: "add" not "added"
Imperative mood: "fix bug" not "fixes bug"
Reference issues: Closes #123, Refs #456
Keep description under 72 characters

Git Safety Protocol

NEVER update git config
NEVER run destructive commands (--force, hard reset) without explicit request
NEVER skip hooks (--no-verify) unless user asks
NEVER force push to main/master
If commit fails due to hooks, fix and create NEW commit (don't amend)

Weekly Installs

18.0K

Repository

github/awesome-copilot

GitHub Stars

27.0K

First Seen

Jan 23, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

opencode17.1K

codex16.9K

gemini-cli16.8K

github-copilot16.8K

kimi-cli16.4K

amp16.3K

React 组合模式指南：Vercel 组件架构最佳实践，提升代码可维护性

102,200 周安装