wf0-restore_skill

This skill restores an existing workspace to resume work across devices by reloading state, branches, and optional worktrees.
  • Shell

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill shotaiuchi/dotclaude --skill wf0-restore

  • SKILL.md1.2 KB

Overview

This skill restores an existing workspace so you can resume work on another machine or recreate a worktree. It automates validation, branch checkout, optional worktree creation, and state updates so the workspace is ready to continue where you left off. It reports a clear next-step command and workspace metadata after completion.

How this skill works

The skill requires jq and git, then resolves the target work-id from the argument, the saved active_work, or an interactive selection. It fetches remotes, determines whether to checkout a local or remote branch, and fails if neither exists. If worktree support is enabled, it creates the worktree and writes the local path into .wf/local.json. Finally it updates active_work in state.json and prints summarized status and the recommended next command.

When to use it

  • Moving development to a different PC and needing the same workspace layout
  • Recovering a workspace after cloning or re-cloning a repository
  • Recreating a lost or accidentally removed worktree for ongoing work
  • Switching machines during a multi-machine workflow
  • Preparing a CI or ephemeral environment to continue an interrupted task

Best practices

  • Ensure jq and git are installed before running the skill
  • Keep state.json and config files committed or backed up so the skill can find work metadata
  • Run git fetch --all --prune manually if you suspect stale refs before restore
  • Verify branch and base exist remotely if not present locally to avoid errors
  • Enable worktree in config only when you want per-work directories maintained

Example use cases

  • Restore the workspace for work-id 123 to continue a code review on a different laptop
  • Recreate a per-feature worktree after cloning the repository on a new build server
  • Resume work automatically by calling the skill with no argument when active_work is set
  • Select from several candidate work-ids when you are unsure which task was active

FAQ

The skill fails early with an error indicating state.json is required and halts to avoid guessing workspace metadata.

How does the skill choose which branch to checkout?

It prefers a matching local branch, falls back to the corresponding remote branch, and errors if neither exists.

Will the skill create the worktree directory for me?

Yes — if config.worktree.enabled is true the skill creates the worktree root and updates .wf/local.json with the path; otherwise it skips worktree steps.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational