How do I install the Localstudio Worktree Refresh skill?

Run npx skillmds@latest add erickwendel/localstudio-worktree-refresh 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.

Is Localstudio Worktree Refresh 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 Localstudio Worktree Refresh?

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 Localstudio Worktree Refresh free to use?

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

Who published Localstudio Worktree Refresh?

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

Localstudio Worktree Refresh by erickwendel

Name: Localstudio Worktree Refresh
Author: erickwendel

Localstudio Worktree Refresh

LocalStudio worktree freshness workflow. Use whenever Codex creates, opens, switches to, resumes, or starts implementation inside a LocalStudio/canva-webai-clone git worktree, before editing code, so the worktree fetches remote main and fast-forwards safely instead of working from an outdated base.

erickwendel e287f2f 2 files · 2.7 KB Updated Sep 17, 2026

File contents

LocalStudio Worktree Refresh

Overview

Use this skill before implementation starts in any LocalStudio worktree. The goal is to update the worktree from origin/main without losing local work or hiding branch divergence.

Refresh Workflow

Inspect the worktree before network or merge commands.

git status --short --branch
git remote get-url origin
git branch --show-current

Stop if the worktree has local changes.
- Do not stash, reset, checkout, or overwrite user changes automatically.
- Report the dirty files and ask before continuing, unless the user explicitly told you those changes are yours to manage.
Fetch the latest remote main.
```
git fetch origin main
```
- If network/sandboxing blocks this command, rerun it with approval/escalation.
- Do this before trusting local origin/main state.
Confirm whether the current HEAD can fast-forward to origin/main.
```
git merge-base --is-ancestor HEAD origin/main
```
Fast-forward only when safe.
```
git merge --ff-only origin/main
```
- This is valid for detached worktrees and branch worktrees when HEAD is an ancestor of origin/main.
- If the command says "Already up to date.", treat the worktree as fresh.
Stop on divergence.
- If HEAD is not an ancestor of origin/main, do not rebase or merge manually.
- Report the branch, git status --short --branch, and ask how the user wants to reconcile the worktree.

Report the refreshed base.

git rev-parse --short HEAD
git log -1 --oneline

Handoff Rules

Mention the exact refresh command sequence used.
If the refresh was skipped because the worktree was dirty or divergent, say that clearly before implementation starts.
Never use git reset --hard, git checkout --, or destructive cleanup as part of this skill unless the user explicitly requested that destructive action.
After refreshing, continue with the task using the repo's other applicable skills, such as writing-typescript for TypeScript/source edits and localstudio-finish-checks before final handoff.

---name: localstudio-worktree-refreshdescription: LocalStudio worktree freshness workflow. Use whenever Codex creates, opens, switches to, resumes, or starts implementation inside a LocalStudio/canva-webai-clone git worktree, before editing code, so the worktree fetches remote main and fast-forwards safely instead of working from an outdated base.---# LocalStudio Worktree Refresh## OverviewUse this skill before implementation starts in any LocalStudio worktree. The goal is to update the worktree from `origin/main` without losing local work or hiding branch divergence.## Refresh Workflow1. Inspect the worktree before network or merge commands. ```bash git status --short --branch git remote get-url origin git branch --show-current ```2. Stop if the worktree has local changes. - Do not stash, reset, checkout, or overwrite user changes automatically. - Report the dirty files and ask before continuing, unless the user explicitly told you those changes are yours to manage.3. Fetch the latest remote main. ```bash git fetch origin main ``` - If network/sandboxing blocks this command, rerun it with approval/escalation. - Do this before trusting local `origin/main` state.4. Confirm whether the current `HEAD` can fast-forward to `origin/main`. ```bash git merge-base --is-ancestor HEAD origin/main ```5. Fast-forward only when safe. ```bash git merge --ff-only origin/main ``` - This is valid for detached worktrees and branch worktrees when `HEAD` is an ancestor of `origin/main`. - If the command says "Already up to date.", treat the worktree as fresh.6. Stop on divergence. - If `HEAD` is not an ancestor of `origin/main`, do not rebase or merge manually. - Report the branch, `git status --short --branch`, and ask how the user wants to reconcile the worktree.7. Report the refreshed base. ```bash git rev-parse --short HEAD git log -1 --oneline ```## Handoff Rules- Mention the exact refresh command sequence used.- If the refresh was skipped because the worktree was dirty or divergent, say that clearly before implementation starts.- Never use `git reset --hard`, `git checkout --`, or destructive cleanup as part of this skill unless the user explicitly requested that destructive action.- After refreshing, continue with the task using the repo's other applicable skills, such as `writing-typescript` for TypeScript/source edits and `localstudio-finish-checks` before final handoff.

Frequently asked questions