菜单
Generates commit messages following Conventional Commits 1.0.0 specification. Use when the user asks to commit changes, write commit messages, or when staging and committing code changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Initialize and configure multi-project memory bank structure. Use when the user asks to set up a memory bank, initialize project context, or create the .memory-bank directory.
Creates and reviews documentation embedded in source code including doc comments, API documentation, and inline documentation. Use when writing code documentation, reviewing doc quality, or adding examples to code.
Creates and manages project-level documentation including READMEs, tutorials, how-to guides, and architectural docs. Use when creating user-facing documentation, writing tutorials, or organizing project documentation following Diataxis framework.
Review code changes for quality, design, and maintainability. Use when reviewing pull requests, code changes, or performing code reviews. Applies general engineering code review standards.
Review Rust code changes for safety, idioms, and patterns. Use when reviewing Rust code, checking ownership and lifetimes, unsafe blocks, error handling, or Rust-specific patterns like builders and typestate.
Enforces Rust development policies including zero warnings, static dispatch preference, minimal Arc usage, and comprehensive testing requirements. Use when reviewing Rust code, writing new Rust code, or checking compliance with project policies.
基于 SOC 职业分类
| name | git-commit |
| description | Generates commit messages following Conventional Commits 1.0.0 specification. Use when the user asks to commit changes, write commit messages, or when staging and committing code changes. |
| metadata | {"author":"aiassisted","version":"1.0"} |
Generates descriptive commit messages following the Conventional Commits specification by analyzing staged changes.
Use this skill when:
Check repository status:
git status
Review staged and unstaged changes:
git diff --staged
git diff
Review recent commit history for style consistency:
git log --oneline -10
Stage relevant files (prefer specific files over git add -A):
git add <specific-files>
Generate commit message following the format below
Create commit using HEREDOC for proper formatting:
git commit -m "$(cat <<'EOF'
<type>(<scope>): <description>
[optional body]
[optional footer]
EOF
)"
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
| Type | Description |
|---|---|
feat | A new feature |
fix | A bug fix |
docs | Documentation only changes |
style | Changes that don't affect code meaning (formatting, etc.) |
refactor | Code change that neither fixes a bug nor adds a feature |
perf | Code change that improves performance |
test | Adding or correcting tests |
build | Changes to build system or external dependencies |
ci | Changes to CI configuration files and scripts |
chore | Other changes that don't modify src or test files |
revert | Reverts a previous commit |
Subject line:
Body (optional):
Footer (optional):
Closes #123BREAKING CHANGE: descriptionIndicate breaking changes by:
feat(api)!: remove endpointBREAKING CHANGE: The endpoint has been removedFeature:
feat(auth): add login with google
Bug fix:
fix: prevent infinite loop in user validation
Breaking change:
feat(api)!: remove deprecated endpoint /v1/users
BREAKING CHANGE: The /v1/users endpoint has been removed. Use /v2/users instead.
Documentation:
docs: update readme with setup instructions
With co-author (AI assisted):
feat(templates): add recursive directory copying
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
For complete Conventional Commits specification details, see references/conventional-commits.md.