sync

Syncs a session branch with its upstream or publishes it to a remote.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/voidful/Aixlarity --skill sync-voidful
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync
Source: https://github.com/voidful/Aixlarity/tree/main/aixlarity-ide/src/vs/sessions/skills/sync
Command: npx skills add https://github.com/voidful/Aixlarity --skill sync-voidful

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a working branch in sync with its upstream remote involves several error-prone Git steps: fetching, checking ahead/behind counts, rebasing, resolving conflicts, and pushing. This Skill automates that entire flow while enforcing safety rules like never force-pushing without approval. ## Core Features & Use Cases - Upstream Sync: Fetches the remote, checks ahead/behind counts, rebases onto the upstream tracking branch, and pushes local commits. - Branch Publishing: Publishes a branch with no upstream by pushing with -u to a chosen remote, asking the user when multiple remotes exist. - Safe Conflict Handling: Resolves rebase conflicts by preserving both sides' intent, and asks the user when resolution is unclear or before aborting. - Use Case: You finished a feature on a session branch and want to pull the latest main changes and push your work. The Skill commits pending changes, rebases onto upstream, pushes, and verifies the branch is fully in sync. ## Quick Start Ask the assistant to sync the current branch with its upstream remote and push any local commits.

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 branch with its upstream remote?

Fetch the upstream remote, check ahead/behind counts with git rev-list, rebase onto the upstream tracking branch, then push local commits. This Skill automates that sequence and verifies the branch ends fully in sync.

How to publish a Git branch that has no upstream?

Run git push -u <remote> HEAD to publish the branch and set upstream tracking in one step. If multiple remotes exist, the Skill asks which remote to use before publishing.

What happens when a rebase hits merge conflicts?

Conflicts are resolved by preserving the intent of both sides, then staged and continued with git rebase --continue. If resolution is unclear, the Skill asks the user, and it can abort the rebase on request.

Does this Skill ever force-push to the remote?

No, force-pushing with --force or --force-with-lease requires explicit user approval. If a push is rejected because a rebase rewrote history, the Skill explains the situation and asks before force-pushing.

What if there are uncommitted changes before syncing?

The Skill checks for uncommitted changes first and uses the commit skill to commit them before continuing. This prevents uncommitted work from interfering with the rebase.