skills.rest
smallorbit
smallorbitCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sync

Synchronize a local Git workspace with the remote develop branch.

Updated Apr 17, 2026
Search Tags:#git#workflow#repository#merge#develop#prune#branch-cleanup
One-click install
npx skills add https://github.com/smallorbit/smallorbit-plugins --skill sync-smallorbit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync
Source: https://github.com/smallorbit/smallorbit-plugins/tree/main/plugins/flowkit/skills/sync
Command: npx skills add https://github.com/smallorbit/smallorbit-plugins --skill sync-smallorbit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Return to a clean develop state after a PR has been merged by switching to develop, pulling the latest changes, and removing local branches that are already merged.

Core Features & Use Cases

  • Switch to develop and pull latest changes from origin to ensure work starts from a current baseline.
  • Prune stale remote-tracking references to keep the repo's refs tidy.
  • Delete local branches that have already been merged into develop (excluding develop, main, staging, and the currently checked-out branch).
  • Generate a concise summary of actions taken and any branches removed for traceability.

Quick Start

Sync your local repository to the latest develop by pulling, pruning, and deleting merged branches.

Frequently Asked Questions about sync

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

FAQPage Schema
How do I clean up local Git branches after merging a pull request?▼

Cleaning up local Git branches after a merge involves switching to develop, pulling latest changes, and deleting branches already merged. This process prunes stale remote-tracking references and removes local branches to maintain a tidy repository.

What is the best way to keep my local develop branch updated with the remote repository?▼

Keeping your local develop branch updated requires switching to develop and pulling the latest changes from origin. This ensures your workspace starts from a current baseline before new development work begins.

How does git fetch prune work for removing stale remote-tracking references?▼

Git fetch prune works by fetching updates from the remote repository and simultaneously deleting stale remote-tracking references. This removes refs to remote branches that no longer exist on the origin server, keeping your local refs tidy.

Which local branches are safe to delete when synchronizing a Git workspace?▼

Local branches that have already been merged into develop are safe to delete when synchronizing a Git workspace. The process excludes develop, main, staging, and the currently checked-out branch to prevent data loss.

Do I need Bash and Git installed to automate branch cleanup and repository syncing?▼

Yes, you need Bash and Git installed to automate branch cleanup and repository syncing. The Skill executes Git commands via Bash to switch branches, fetch updates, prune stale refs, and delete merged local branches.

Why should I prune stale remote-tracking references in my Git repository?▼

You should prune stale remote-tracking references in your Git repository to keep the repo's refs tidy. Pruning removes references to remote branches that have been deleted on the origin server, preventing branch list clutter and potential confusion.

Related Skills

Explore More Software Engineering Skills→
inspedralbesinspedralbes

speckit-git-remote

Detect Git remote URLs and extract owner and repository names.

Official
Intermediate
samjonestersamjonester
5

mozart-wtp-new-worktree

Create or resume a Mozart development worktree via WTP checkout flow.

Community
Intermediate
GEOS-ESMGEOS-ESM
43

github-workflow

Explains Git/GitHub workflow for MAPL including branching, commits, and pull requests.

Official
Intermediate
notquenotque
415

pr-cleanup

Automate safe local Git branch cleanup after PR merges.

Community
Advanced