How do I install the Worktree Workflow skill?

Run npx skillmds@latest add different-ai/worktree-workflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Worktree Workflow skill do?

Enforce a worktree-per-task workflow with regular commits and pushes. Triggers when user mentions: - "create a worktree" - "commit regularly" - "push changes" It is listed under Productivity on SkillMD.

Is Worktree Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Worktree Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Worktree Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Worktree Workflow?

different-ai (@different-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Worktree Workflow by different-ai — Agent Skill

Name: Worktree Workflow
Author: different-ai

File contents

Quick Usage (Already Configured)

Start a task with a fresh worktree

.opencode/skills/worktree-workflow/scripts/start-task-worktree.sh "task-name"

Commit regularly and push

.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)

Ensure you are in a git repo with origin configured.
Optional: set BASE_BRANCH or WORKTREES_DIR in your shell.

Frequently asked questions