worktree-workflow
Enforce a worktree-per-task workflow with regular commits and pushes. Triggers when user mentions: - "create a worktree" - "commit regularly" - "push changes"
Informations de source
- Dépôt
- different-ai/openwork-hub
- Dernière activité de la source
- 11 février 2026 à 01:43
- Langue détectée de SKILL.md
- anglais
- Étoiles
- 34
- Forks
- 13
Options d'installation
Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.
Vérifiez les fichiers source
Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.
Explorateur de fichiers
4 fichiersAffichage de SKILL.md
SKILL.md
Instructions source · Aperçu en lecture seule- 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.
Voir sur GitHub