菜单
Git branch workflow for autonomous work. Apply when implementing features, fixes, or any code changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | branch-workflow |
| description | Git branch workflow for autonomous work. Apply when implementing features, fixes, or any code changes. |
All work happens on branches. Main stays clean. Tako reviews before merge.
feat/TASK-ID-short-description # New features
fix/TASK-ID-short-description # Bug fixes
docs/TASK-ID-short-description # Documentation
research/TASK-ID-description # Exploration
refactor/TASK-ID-description # Code improvements
Examples:
feat/TSC-001-plugin-supervisorfix/MSC-023-dashboard-crashdocs/TORIS-005-case-studyTASK-ID: Brief description of change
- Detail 1
- Detail 2
Co-Authored-By: Claude <co-author>
Good commits:
git checkout main
git pull origin main
git checkout -b feat/TASK-ID-description
# Commit often
git add -A
git commit -m "TASK-ID: Implement X"
# Push periodically
git push -u origin feat/TASK-ID-description
# Ensure tests pass
cargo test # or npm test, pytest, etc.
# Push final state
git push
# Log completion (megg or BACKLOG.md)
git push --force).megg/blocked.md or commit messageTako reviews branches by:
# See all work
git branch -a
# Review specific branch
git log main..feat/BRANCH-NAME
git diff main..feat/BRANCH-NAME
# Merge if good
git checkout main
git merge feat/BRANCH-NAME
For OpenSpec changes:
feat/add-plugin-systemFor critical bugs in production:
hotfix/description branchRead Claude Code documentation to learn about features, capabilities, hooks, skills, MCP, subagents, and how to use Claude Code effectively.
Close a dev-cycle session, capture learnings, and optionally commit. Use when development work is complete and ready to wrap up.
Fully autonomous development mode. Spec in, production-ready software out. Claude makes decisions, uses agents, commits locally. Only stops for hard blockers.
Run QA checks on current work. Tests, linting, type checking, build verification. Use during or after development to catch issues early.
Release candidate preparation. Final checks before merge - QA, security, review, changelog. The last gate before shipping.
Security audit with Sentinel. Checks for vulnerabilities, secrets, dependencies, and security best practices. Use before shipping or when working on auth/crypto/sensitive areas.