菜单
Write clear, conventional commit messages that communicate changes effectively
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
A skill whose only resource is a binary asset for e2e binary-handling tests
A valid test skill with all features
Design RESTful APIs following best practices for consistency, usability, and scalability
Systematic code review methodology for identifying issues, suggesting improvements, and ensuring code quality
Write secure, efficient Dockerfiles following container best practices
Identify security vulnerabilities and recommend fixes based on OWASP guidelines
| name | git-commit |
| description | Write clear, conventional commit messages that communicate changes effectively |
| license | Apache-2.0 |
| compatibility | claude-3 |
| metadata | {"author":"skills-mcp","version":"1.0","category":"development"} |
| allowed-tools | Bash Read |
Write commit messages that are clear, consistent, and useful for understanding project history.
<type>(<scope>): <subject>
<body>
<footer>
| Type | Description |
|---|---|
feat | New feature for users |
fix | Bug fix for users |
docs | Documentation changes |
style | Formatting, missing semicolons, etc. |
refactor | Code change that neither fixes a bug nor adds a feature |
perf | Performance improvement |
test | Adding or updating tests |
build | Changes to build system or dependencies |
ci | CI configuration changes |
chore | Other changes that don't modify src or test files |
revert | Reverts a previous commit |
Optional. Describes the section of codebase affected:
auth, api, db, ui, config, etc.BREAKING CHANGE: <description> for breaking changesFixes #123 or Closes #456 for issue referencesCo-authored-by: Name <email> for pair programmingfeat(auth): add password reset functionality
fix(api): handle null response from payment provider
The payment API sometimes returns null instead of an error object
when the service is degraded. This caused unhandled exceptions
in production.
Fixes #892
feat(api)!: change authentication to use JWT tokens
Migrate from session-based auth to JWT tokens for better
scalability and stateless operation.
BREAKING CHANGE: All API clients must now include JWT token
in Authorization header instead of session cookie.
docs: update API reference with rate limiting info
refactor(db): extract query builder into separate module
No functional changes. Improves testability and
reduces coupling between repository and query logic.
# Stage specific files
git add <file1> <file2>
# Interactive staging
git add -p
# Commit with message
git commit -m "feat: add new feature"
# Commit with body (opens editor)
git commit
# Amend last commit
git commit --amend