skills.rest
jaballer
jaballerCOMMUNITY
Explore all skills by this author →
GitHub

ftf-sync-master

Synchronize a local FiveTwoFive repository with the latest master branch.

2|Updated Jun 14, 2020
Search Tags:#version control#code maintenance#GitHub#branch management#repo synchronization
One-click install
npx skills add https://github.com/jaballer/fivetwofive-cw --skill ftf-sync-master
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ftf-sync-master
Source: https://github.com/jaballer/fivetwofive-cw/tree/main/.claude/skills/ftf-sync-master
Command: npx skills add https://github.com/jaballer/fivetwofive-cw --skill ftf-sync-master

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that the local FiveTwoFive repository is synchronized with the latest master branch, removing any stale local branches, and preparing the workspace for new tasks.

Core Features & Use Cases

  • Syncs Local State: Keeps the local repository state clean and in sync with the latest master branch.
  • Removes Stale Branches: Identifies and deletes branches that are safe to remove after their corresponding pull requests are merged.
  • Use Case: Ideal for use after merging a pull request, switching tasks, or starting a new session to ensure the local repository is up-to-date.

Quick Start

Use the ftf-sync-master skill to sync the local master branch and remove any stale branches.

Frequently Asked Questions about ftf-sync-master

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

FAQPage Schema
How do I sync my local repository with the latest master branch after merging a pull request?▼

Syncing your local repository with the master branch involves pulling the latest updates and removing stale local branches. This ensures your local state is clean, up-to-date, and prepared for starting new tasks.

What is the best way to remove stale branches in a GitHub repository?▼

The best way to remove stale branches is to identify and delete local branches that are safe to remove after their corresponding pull requests are merged. This keeps your local repository state clean and synchronized with the master branch.

When should I clean up local branches in my version control workflow?▼

You should clean up local branches when switching tasks, starting a new session, or after merging a pull request. Removing stale branches prevents clutter and ensures your local repository remains synchronized with the master branch.

Do I need GitHub to synchronize my local master branch and delete merged branches?▼

Using GitHub for version control is required to effectively identify merged pull requests and safely remove stale local branches. This ensures your local master branch synchronizes properly by pulling the latest repository updates.

Why does my local repository have stale branches after a pull request is merged?▼

Your local repository has stale branches because local copies are not automatically deleted when a pull request is merged on GitHub. You must explicitly synchronize your local state to identify and remove these obsolete branches.

Related Skills

Explore More Software Engineering Skills→
Tx1207Tx1207
5

project-creator

Create a new project from a template, initialize uv, and configure a local Git repository.

Community
Advanced
Soul-Brews-StudioSoul-Brews-Studio
116

merged

Switch to main, pull latest changes, and delete merged branches.

Official
Basic
KrismithReddy12KrismithReddy12

land-and-deploy

Merge pull requests, trigger CI/CD pipelines, and validate production health.

Community
Advanced
AvatarGanymedeAvatarGanymede

clean-branches

Delete local git branches and worktrees deleted on the remote.

Community
Basic