sync

Synchronize a Git-Spice repository with its remote and trunk.

8|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/jfmyers9/agent --skill sync-jfmyers9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync
Source: https://github.com/jfmyers9/agent/tree/main/harnesses/pi/extensions/git-tool/skill-resources/git-spice/sync
Command: npx skills add https://github.com/jfmyers9/agent --skill sync-jfmyers9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps a Git-Spice repository in sync with its remote and trunk, ensuring local stacks stay up-to-date and restack after changes.

Core Features & Use Cases

  • Pulls latest remote changes for the current stack.
  • Restack-aware synchronization to realign the local stack after updates.
  • Reports remote updates, deleted merged branches, and stack synchronization results.

Quick Start

Run the sync command for your current stack to pull remote changes and restack.

Frequently Asked Questions about sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync a Git-Spice stack with remote changes?

Git-Spice stack synchronization requires running gs repo sync --restack to pull remote trunk updates and realign local feature branches. It triggers the restack mechanism to refresh local state and reports synchronized branches, deleted merged branches, and remote updates.

Why do I need to restack my repository after pulling remote updates?

Restacking after pulling remote updates is necessary because trunk changes shift the base of local feature branches. Synchronization with the restack mechanism realigns your stack onto the updated trunk, preventing stale branch states and ensuring local development stays current with the remote repository.

How does Git-Spice handle restack conflicts during stack synchronization?

Git-Spice handles restack conflicts during synchronization by invoking its dedicated restack mechanism. When running gs repo sync --restack, the process attempts to realign local branches onto the updated trunk and reports any conflicts through the restack process for manual resolution.

Can I use Git-Spice sync for stack-based workflows across local development and Change Requests?

Git-Spice sync supports stack-based workflows across local development, feature branches, and Change Requests. It synchronizes the repository with its remote and trunk to ensure local stacks stay up-to-date wherever restacking is required after a remote update.

What information does Git-Spice report after synchronizing a repository?

After synchronizing a repository, Git-Spice reports remote updates, deleted merged branches, and stack synchronization results. This output confirms which branches were successfully restacked and highlights any changes pulled from the remote trunk.