smithery.ai

worktree-workflow

Enforce a worktree-per-task workflow with regular commits and pushes. Triggers when user mentions: - "create a worktree" - "commit regularly" - "push changes"

First seen Mar 22, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Declared

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents opencode

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,321 B
  • docs SUMMARY.md 189 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

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)

  1. Ensure you are in a git repo with origin configured.
  2. Optional: set BASEBRANCH or WORKTREESDIR in your shell.