一键导入
commit
Create conventional git commits from all uncommitted changes. Extracts ticket numbers from branch names and uses conventional commit format.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Create conventional git commits from all uncommitted changes. Extracts ticket numbers from branch names and uses conventional commit format.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create conventional git commits from staged changes only. Extracts ticket numbers from branch names and uses conventional commit format.
Push current branch and create a GitHub pull request with proper formatting. Use when you have committed changes ready to be pushed and want to open a PR with a well-structured description.
Analyze and fix GitHub issues. Use when given a GitHub issue URL or number to investigate, understand the root cause, implement a fix, and verify the solution works.
Interview users in-depth to create detailed feature specifications. Use when gathering requirements for a new feature, understanding user needs, or creating PRDs. Asks probing questions about technical implementation, UI/UX, and edge cases.
Generate and maintain project documentation. Use when initializing docs for a new project, updating architecture docs, or creating feature specifications. Creates ai_docs/ and ai_specs/ folders with structured documentation.
Update implementation plan files by marking completed tasks and committing changes. Use after completing tasks in a phased implementation to track progress and keep the plan file current.
| name | commit |
| description | Create conventional git commits from all uncommitted changes. Extracts ticket numbers from branch names and uses conventional commit format. |
| allowed-tools | Bash |
Create a git commit from all uncommitted changes using Conventional Commits format with ticket extraction.
git add -A to stage all changesgit branch --show-current to extract ticket numbergit diff --cached to see what will be committedtype(scope): TICKET-123 subject
[optional body]
If no ticket found in branch name, omit it:
type(scope): subject
Extract ticket from branch name patterns:
feature/TEC-16401-description → TEC-16401bugfix/PROJ-283-fix-login → PROJ-283hotfix/APP-12345-critical → APP-12345[A-Z]+-\d+ (uppercase prefix, dash, numbers)| Type | Description |
|---|---|
feat | New feature |
fix | Bug fix |
docs | Documentation only |
style | Formatting, missing semicolons (no code change) |
refactor | Code restructuring (no feature/fix) |
perf | Performance improvement |
test | Adding/updating tests |
build | Build system or dependencies |
ci | CI configuration |
chore | Maintenance tasks |
revert | Revert previous commit |
auth, ui, api)With ticket (from branch feature/TEC-16401-auth-improvements):
feat(auth): TEC-16401 add biometric login support
fix(cart): PROJ-283 resolve quantity update bug
Without ticket (from branch main or develop):
refactor: simplify user repository data mapping
docs: update API endpoint documentation