一键在 Manus 中运行任何 Skill

worktree-workflow

星标59

分支7

更新时间2026年2月10日 07:21

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

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

different-ai

different-ai/the-factory

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

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.

同仓库更多 Skills

同仓库

using-openwork-with-chrome-mcp

different-ai/the-factory

Drive the OpenWork dev renderer with Chrome MCP and verify workspace UI flows. Triggers when user mentions: - "use Chrome MCP with OpenWork" - "hook up to pnpm dev renderer" - "add an OpenWork workspace through the UI"

2026-05-0659

make-pr

different-ai/the-factory

Create a PR with structured evidence: build verification, UI screenshots uploaded to an ephemeral host, API test results, and a verification comment. No screenshots committed to the repo. Triggers when user mentions: - "create a pr" - "make a pr" - "open a pr" - "push and pr"

2026-05-0559

den-test-instructions

different-ai/the-factory

Boot up the Den dev stack and the OpenWork desktop app locally, then test common flows like sign-in, dashboard, and telemetry. Triggers when user mentions: - "test den" - "test the app locally" - "boot up den" - "den dev flow" - "test sign in"

2026-05-0559

changelog-release-tracker

different-ai/the-factory

Generate or update the internal OpenWork release changelog tracker as plain markdown release sections. Triggers when user mentions: - "generate changelog markdown" - "track this release" - "add a changelog entry"

2026-04-0559

cupid-app-architecture

different-ai/the-factory

CUPID app architecture guidance for apps/app/src/app/**

2026-03-2959

vercel-env-vars

different-ai/the-factory

Manage Vercel environment variables for OpenWork projects from the CLI, including linking the local app directory first. Triggers when user mentions: - "add a vercel env var" - "set a vercel env var" - "vercel environment variable"

2026-03-2359

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

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