worktree-workflow
Enforce a worktree-per-task workflow with regular commits and pushes. Triggers when user mentions: - "create a worktree" - "commit regularly" - "push changes"
来源信息
- 仓库
- different-ai/the-factory
- 最近来源活动
- 2026年2月10日 07:21
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 70
- 分支
- 9
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
4 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- worktree-workflow
- description
- Enforce a worktree-per-task workflow with regular commits and pushes. Triggers when user mentions: - "create a worktree" - "commit regularly" - "push changes"
## Quick Usage (Already Configured)
### Start a task with a fresh worktree
```bash
.opencode/skills/worktree-workflow/scripts/start-task-worktree.sh "task-name"
```
### Commit regularly and push
```bash
.opencode/skills/worktree-workflow/scripts/regular-commit.sh "message describing why"
```
## Behavior
- Any task that changes files should begin by creating a dedicated worktree.
- Commit after each meaningful chunk of work.
- Push the branch after each commit.
- Submodules are initialized in the new worktree.
## Related skills
- For UX PR flows with screenshots, use `.opencode/skills/worktree-ux-pr/SKILL.md`.
## Common Gotchas
- Use a short, kebab-case task name; it becomes the branch suffix.
- If your default branch is not `main`, set `BASE_BRANCH`.
- If you update submodule pins, make sure the target submodule SHA is reachable from a remote branch/tag (avoid pinning to commits that were only on a force-pushed ref).
## First-Time Setup (If Not Configured)
1. Ensure you are in a git repo with `origin` configured.
2. Optional: set `BASE_BRANCH` or `WORKTREES_DIR` in your shell.
在 GitHub 查看