How this skill is triggered — by the user, by Claude, or both
Slash command
/git-tools:workflowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
团队工作流管理技能 - 协作规范、自动化流程和最佳实践。
团队工作流管理技能 - 协作规范、自动化流程和最佳实践。
# 初始化工作流
/workflow init --template gitflow
# 创建功能分支
/workflow start-feature PROJ-123 "用户认证"
# 分配代码审查
/workflow assign-review
# 发布版本
/workflow release --type minor
main (生产)
└── develop (开发)
├── feature/* → 开发完成后合并到 develop
├── release/* → 从 develop 创建,测试后合并到 main
└── hotfix/* → 从 main 创建,修复后合并到 main 和 develop
初始化命令:
/workflow init --template gitflow
# 创建:main, develop 分支
# 配置:分支保护规则
main (始终可部署)
└── feature/* → 开发完成后创建 PR 合并到 main
初始化命令:
/workflow init --template github-flow
# 配置:PR 模板、CI/CD
main (主干)
└── short-lived/* → 短期分支(<1天),快速合并
# 创建功能分支(自动命名)
/workflow start-feature PROJ-123 "用户认证"
# 等同于
git checkout develop
git pull origin develop
git checkout -b feature/PROJ-123-user-auth
# 基于代码所有权分配
/workflow assign-review --strategy codeowners
# 基于负载均衡分配
/workflow assign-review --strategy balanced
# 随机分配(排除作者)
/workflow assign-review --strategy random
# 查看待审查列表
/workflow review-status --pending
# 查看我的审查任务
/workflow review-status --mine
# 创建发布分支
/workflow release --type minor --version 2.1.0
# 执行步骤:
# 1. 从 develop 创建 release/2.1.0
# 2. 更新版本号
# 3. 更新 CHANGELOG
# 4. 测试和修复
# 5. 合并到 main 并打标签
# 6. 合并回 develop
# 7. 推送到远程
{
"release": {
"autoChangelog": true,
"autoTag": true,
"notifySlack": true,
"environments": ["staging", "production"]
}
}
# 关联分支到 JIRA 工单
/workflow link-jira PROJ-123
# 自动更新工单状态
# feature 开始 → In Progress
# PR 创建 → In Review
# 合并完成 → Done
# 配置通知
/workflow config-slack --channel "#dev-notifications"
# 触发通知的事件:
# - 新 PR 创建
# - 审查请求
# - 合并完成
# - 发布开始/完成
{
"workflow": {
"template": "gitflow",
"autoReview": true,
"autoRelease": false,
"integrations": ["slack", "jira"],
"branchProtection": {
"main": { "requiredReviews": 2, "requiredStatusChecks": ["ci"] },
"develop": { "requiredReviews": 1 }
}
}
}
npx claudepluginhub protagonistss/ithinku-plugins --plugin git-toolsGuides teams in choosing a branching strategy (trunk-based, GitHub Flow, Git Flow, GitLab Flow), defining commit conventions (Conventional Commits), setting up PR workflows, managing releases, and establishing git standards.
Feature branches, commit hygiene, rebasing vs. merging, and collaborative workflows.
Guides Git workflows with branching strategies (GitHub Flow, Git Flow), conventional commit messages, branch naming, PR templates, and operations like rebase. Use for Git ops, commits, branches, team workflows.