skills.rest
LightForgeLabsStudio
LightForgeLabsStudioOFFICIAL
Explore all skills by this author →
GitHub

sync

Synchronize a Git branch with its remote counterpart.

2|Updated Dec 11, 2025
Search Tags:#git#push#sync#rebase#branch#clean state
One-click install
npx skills add https://github.com/LightForgeLabsStudio/AIDE --skill sync-lightforgelabsstudio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync
Source: https://github.com/LightForgeLabsStudio/AIDE/tree/main/skills/sync
Command: npx skills add https://github.com/LightForgeLabsStudio/AIDE --skill sync-lightforgelabsstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures your local branch is up-to-date with the remote and that all your work is pushed, preventing merge conflicts and lost commits.

Core Features & Use Cases

  • Branch Synchronization: Pulls the latest changes from the remote and pushes local commits.
  • Clean State Verification: Checks if the working directory is clean before and after syncing.
  • Safety First: Avoids syncing on the main branch by default and stops if rebasing fails.
  • Use Case: Before finishing a work session or creating a pull request, use this Skill to ensure your code is safely backed up and current.

Quick Start

Run the sync skill to update your branch with the remote and push your changes.

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 remote and verify a clean state?▼

To sync a Git branch, pull latest remote changes and push local commits while verifying the working directory is clean before and after, ensuring a safe end-of-session state with no merge conflicts or lost commits.

What is the best way to push committed changes before concluding a work session?▼

The best way to push committed changes before ending a session is running a branch synchronization that pulls remote updates, pushes local commits, and verifies a clean working directory to prevent data loss.

Can I sync changes directly on the main branch?▼

No, syncing on the main branch is avoided by default for safety. Branch synchronization targets feature branches to ensure standard Git practices and prevent accidental direct pushes to the protected main branch.

Does Git branch synchronization stop if a rebase fails?▼

Yes, branch synchronization stops immediately if a rebase fails. This safety-first mechanism prevents corrupting your commit history or losing uncommitted work during the remote update process.

Can I perform a dry-run execution to test Git branch syncing?▼

Yes, optional flags support dry-run execution for Git branch synchronization. This allows you to preview remote pull and local push operations without modifying your actual working directory or commit history.

Why does Git branch synchronization check for a clean working directory?▼

Git branch synchronization checks for a clean working directory before and after pulling remote changes and pushing local commits to prevent merge conflicts, ensuring all work is safely backed up and current.

Related Skills

Explore More Software Engineering Skills→
EdanStarfireEdanStarfire
15

git-state-validator

Validate Git repository state before branching, merging, or pulling.

Community
Basic
mkalkeremkalkere
4

pr-create

Create GitHub pull requests and request code reviews from feature branches.

Community
Advanced
bmsull560bmsull560

jr-rebase

Resolves git rebase conflicts in feature branches via guided marker resolution.

Community
Intermediate
MarcoAntoliniMarcoAntolini
1

git-fetch-pull

Execute git fetch and pull commands to synchronize local branches with remote repositories.

Community
Intermediate