npx skills add https://github.com/acbcdev/claude-code --skill 'Conventional Commits - Advanced'为高级场景直接创建约定式提交。
检查仓库状态:
git status
git diff --staged
git log --oneline -5
如果仓库处于冲突状态或没有暂存的更改,请停止操作。
查看暂存的内容并确定:
类型 - 这是什么类型的更改?
feat - 新功能fix - 错误修复docs - 仅文档style - 仅格式refactor - 代码重构(无行为变更)perf - 性能改进test - 测试变更build - 构建/依赖项变更ci - CI/CD 变更chore - 维护/工具变更范围 - 项目的哪个部分受到影响?
auth、api、ui、db)user 而非 users)破坏性变更? - 这会破坏现有功能吗?
如果是:使用 ! 标记并包含 BREAKING CHANGE: 页脚
问题引用? - 这链接到任何问题吗?
Fixes #123 - 用于错误修复Closes #456 - 用于任何问题类型Relates to #789 - 用于引用但不关闭type(scope): short description
示例:
feat(auth): add two-factor authenticationfix(payment): prevent duplicate chargesdocs(readme): add installation guide标题规则:
在以下情况下添加正文:
格式:
示例:
feat(auth): add JWT token support
Implement JWT tokens for stateless authentication across the API.
- Add JWT generation and validation service
- Update authentication middleware
- Add refresh token endpoint
- Add token expiration handling
为破坏性变更或问题引用添加页脚。
破坏性变更示例:
feat(api)!: restructure response format
BREAKING CHANGE: User endpoints now return nested structure
Before:
{ "id": 1, "name": "John" }
After:
{ "user": { "id": 1, "name": "John" } }
Migration: Update clients to access response.user
Closes #567
问题引用示例:
fix(payment): prevent duplicate charges
Users could be charged twice when clicking submit multiple times.
- Add idempotency keys to payment requests
- Disable button during processing
- Add concurrency tests
Fixes #834
构建完整消息并使用 heredoc 格式:
git commit -m "$(cat <<'EOF'
type(scope): description
Body explaining the change if needed.
BREAKING CHANGE: or issue references if needed
Fixes #123
EOF
)"
重要:在 <<'EOF' 中使用单引号以防止 shell 扩展。
提交后,验证:
git log -1 --format=fuller
检查:
始终执行:
切勿执行:
如果更改包含多个不相关的内容:
示例:
# Commit 1
feat(api): add user endpoint
# Commit 2
chore(deps): upgrade TypeScript
# Commit 3
docs: update API documentation
详细示例和模式:EXAMPLE.md
每周安装次数
–
仓库
首次出现
–
Create conventional commits directly for advanced scenarios.
Check the repository state:
git status
git diff --staged
git log --oneline -5
Stop if repository is in conflict state or no changes are staged.
Look at what's staged and determine:
Type - What kind of change is this?
feat - new featurefix - bug fixdocs - documentation onlystyle - formatting onlyrefactor - code restructure (no behavior change)perf - performance improvement广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
test - test changesbuild - build/dependency changesci - CI/CD changeschore - maintenance/toolingScope - What part of the project is affected?
auth, api, ui, db)user not users)Breaking changes? - Does this break existing functionality?
If yes: Use ! marker and include BREAKING CHANGE: footer
Issue references? - Is this linked to any issues?
Fixes #123 - for bug fixesCloses #456 - for any issue typeRelates to #789 - for references without closingtype(scope): short description
Examples:
feat(auth): add two-factor authenticationfix(payment): prevent duplicate chargesdocs(readme): add installation guideRules for header:
Add a body when:
Format:
Example:
feat(auth): add JWT token support
Implement JWT tokens for stateless authentication across the API.
- Add JWT generation and validation service
- Update authentication middleware
- Add refresh token endpoint
- Add token expiration handling
Add footer for breaking changes or issue references.
Breaking change example :
feat(api)!: restructure response format
BREAKING CHANGE: User endpoints now return nested structure
Before:
{ "id": 1, "name": "John" }
After:
{ "user": { "id": 1, "name": "John" } }
Migration: Update clients to access response.user
Closes #567
Issue reference example :
fix(payment): prevent duplicate charges
Users could be charged twice when clicking submit multiple times.
- Add idempotency keys to payment requests
- Disable button during processing
- Add concurrency tests
Fixes #834
Build the complete message and use heredoc format:
git commit -m "$(cat <<'EOF'
type(scope): description
Body explaining the change if needed.
BREAKING CHANGE: or issue references if needed
Fixes #123
EOF
)"
Important: Use single quotes in <<'EOF' to prevent shell expansion.
After committing, verify:
git log -1 --format=fuller
Check that:
Always do :
Never do :
If changes contain multiple unrelated things:
Example:
# Commit 1
feat(api): add user endpoint
# Commit 2
chore(deps): upgrade TypeScript
# Commit 3
docs: update API documentation
Detailed examples and patterns: EXAMPLE.md
Weekly Installs
–
Repository
First Seen
–
Azure Data Explorer (Kusto) 查询技能:KQL数据分析、日志遥测与时间序列处理
114,200 周安装