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/openwork-hub
- 최근 소스 활동
- 2026년 2월 11일 01:43
- 감지된 SKILL.md 언어
- 영어
- 스타
- 34
- 포크
- 13
설치 방법
기본적으로 소스를 먼저 확인하는 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
skills/worktree-workflow/scripts/start-task-worktree.sh "task-name"
```
### Commit regularly and push
```bash
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 `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에서 보기