菜单
Generate and execute git commits following conventional commit format. Use when the user wants to commit changes, create a commit, or says "/commit". Analyzes staged/unstaged changes and creates properly formatted commit messages with type, optional scope, and descriptive subject.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Update CLAUDE.md sections through interactive Q&A. Use when the user wants to update project documentation, refresh CLAUDE.md content, or says "/update-claude-md". Guides user through questions to update auto-generated sections (overview, objectives, commands, notes).
Codify discovered processes into standalone, reusable Python scripts. Use when the user has figured out a process (API integration, data pipeline, automation task) and wants to turn it into a reusable script, or when the user says "/create-script".
Guide feature development through contract establishment and UI design phases. Use when discussing, designing, or planning a new feature that is not yet implemented. Ensures requirements are clarified, acceptance criteria defined, and UI layouts drafted before any code is written.
Meta-skill by Anthropic to help guide creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Create GitHub pull requests with properly structured descriptions. Use when the user explicitly asks to create a PR, open a pull request, or says "/create-pr". Analyzes commits and changes to generate clear PR descriptions with summary, changes list, and UI changes when applicable.
Create task tickets with proper numbering, template structure, and ticket-list.md updates. Use when the user wants to create a ticket, add a task, or says "/create-ticket". Automatically finds the next ticket number, creates the ticket file, and updates the centralized ticket list.
| name | commit |
| description | Generate and execute git commits following conventional commit format. Use when the user wants to commit changes, create a commit, or says "/commit". Analyzes staged/unstaged changes and creates properly formatted commit messages with type, optional scope, and descriptive subject. |
Generate conventional commit messages and execute commits automatically.
git status (never use -uall flag) and git diff to analyze changesgit log --oneline -5 to see recent commit stylegit add<type>(<scope>): <subject>
<body>
<footer>
| Type | Use for |
|---|---|
feat | New feature or functionality |
fix | Bug fix |
docs | Documentation only |
style | Formatting, semicolons, no code change |
refactor | Code change that neither fixes nor adds |
test | Adding or modifying tests |
chore | Maintenance, deps, build process |
perf | Performance improvements |
Optional. Include when it adds clarity about what area is affected:
feat(auth): - authentication relatedfix(api): - API relateddocs: - scope omitted when obviousAdd when the subject alone doesn't fully explain the change. Wrap at 72 characters.
BREAKING CHANGE: descriptionCloses #123Use a HEREDOC for proper formatting:
git commit -m "$(cat <<'EOF'
<type>(<scope>): <subject>
<body if needed>
EOF
)"
Single file change:
fix(auth): handle expired tokens gracefully
Multiple related changes:
feat(api): add email notifications for shipped orders
Send confirmation email when order status changes to shipped.
Includes tracking number and estimated delivery date.
Breaking change:
refactor(config)!: migrate to environment-based configuration
BREAKING CHANGE: config.json no longer supported, use .env files