Run

To pull the latest code and launch Foundry locally, this skill automates fetching the specified branch, checking out main or test, synchronizing dependencies, and launching the GUI before restoring your previous state.

When updating your local Foundry development environment, the skill safely auto-stashes dirty worktrees before pulling and checking out branches, then restores your uncommitted changes after the application exits.

Yes, you need both git and uv installed, along with access to the main or test branches, to run an automated Foundry branch update and synchronize dependencies successfully.

Yes, you can synchronize dependencies and launch the Foundry GUI deterministically on either the main or test branch, ensuring a consistent environment by coordinating fetch, checkout, and pull operations.

Your local Foundry launch restores stashed work after the app exits to preserve your in-progress changes, meaning the freshly pulled code runs first and your dirty worktree is reapplied safely afterward.

The best way to manage remote Foundry workflows is automating the local update cycle: fetch server-side changes, checkout target branches, sync dependencies, launch locally, and restore state automatically.