一键导入
flow-sync
Flow: Sync - Push WIP to Remote for Cross-Machine Pickup - Push the current branch to the remote so you can continue work on another machine. ...
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Flow: Sync - Push WIP to Remote for Cross-Machine Pickup - Push the current branch to the remote so you can continue work on another machine. ...
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Analyze a GitHub-backed repository's open issues, pull requests, branches, and worktrees to recommend the next unclaimed issue or cleanup action. Use when Codex is asked what to work on next, to triage project backlog, or to choose between open GitHub issues.
Analyze a GitHub-backed repository's open issues, pull requests, branches, and worktrees to recommend the next unclaimed issue or cleanup action. Use when Codex is asked what to work on next, to triage project backlog, or to choose between open GitHub issues.
Launch a bounded, read-only Claude Code session through the Claude Agent SDK to review the current issue-branch diff and advise Codex. Use when the user requests a Claude or cross-model code review, or when flow-auto remains stuck after two materially distinct attempts and needs implementation support.
Launch a bounded, read-only Claude Code session through the Claude Agent SDK to review the current issue-branch diff and advise Codex. Use when the user requests a Claude or cross-model code review, or when flow-auto remains stuck after two materially distinct attempts and needs implementation support.
Bootstrap Codex Power Pack host wiring with explicit consent for every global change
Report installed Codex Power Pack plugins, host pointers, health, and drift without changing the machine
| name | flow-sync |
| description | Flow: Sync - Push WIP to Remote for Cross-Machine Pickup - Push the current branch to the remote so you can continue work on another machine. ... |
Generated from a Claude Code command. Where the procedure references these Claude-only surfaces, adapt as follows:
$FLOW_WORKTREE_BASE/<repo>-<branch> when configured, otherwise as a visible sibling ../<repo>-<branch>; enter with cd and clean up with git worktree remove. Never use Claude's hidden worktree directory.Push the current branch to the remote so you can continue work on another machine. Optional feature - most users won't need this.
None. Operates on the current worktree/branch.
When the user invokes /flow-sync, perform these steps:
# Ensure we're in a git repo
git rev-parse --show-toplevel
# Get current branch
BRANCH=$(git branch --show-current)
main or master: STOP. Report: "Cannot sync main branch. Use /flow-start <issue> to create a worktree first."issue-* branch: Warn but allow (user may have custom branch names).# Check working tree status
git status --short
git add -A
git commit -m "wip: sync work in progress
Auto-committed by /flow-sync for cross-machine pickup.
This commit will be squash-merged - no need to clean up."
Report: "Auto-committed WIP changes."git push -u origin "$BRANCH"
git pull --rebase origin "$BRANCH" to resolve.Synced branch to remote.
Branch: issue-42-fix-login-bug
Remote: origin
To continue on another machine:
/flow-start 42
→ Detects remote branch and creates worktree from it
/flow-start.git pull --rebase to reconcile.issue-<N>-<slug> branch, not on worktree paths, so the native ../<repo>-<branch>/ location (which is per-workstation and gitignored) does not affect it./flow-start already handles the receiving end: it detects the remote branch and, because the native EnterWorktree tool cannot check out an existing remote branch, adds a worktree tracking it with git worktree add and then switches in with EnterWorktree(path=...)./flow-merge uses squash-merge, collapsing all commits into one clean commit.