sync-skills

Push local skill changes to a GitHub repository with conditional checks.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/akshatdalton/skills --skill sync-skills-akshatdalton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-skills
Source: https://github.com/akshatdalton/skills/tree/main/sync-skills
Command: npx skills add https://github.com/akshatdalton/skills --skill sync-skills-akshatdalton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the need to synchronize local skill changes with a GitHub repository, ensuring that all changes are up-to-date and available across all machines.

Core Features & Use Cases

  • Sync Skill Changes: Pushes all local skill changes to a GitHub repository, allowing for collaboration and version control.
  • Single Command Automation: Executes a single command that handles stashing, pulling, rebasing, and popping changes, simplifying the sync process.
  • Conditional Checks: Checks for staged changes and confirms if they need to be pushed, avoiding unnecessary commits.
  • Commit and Push: Builds a commit message based on changed files and pushes the changes to the GitHub repository.
  • Result Reporting: Reports the commit hash and confirms the push success.
  • Pull Reminder: Reminds the user to pull changes on other machines to update their skill repository.
  • Use Case: Ideal for developers and operators working on Claude Code skills who need to ensure that their changes are reflected in the shared GitHub repository.

Quick Start

Run the command "/sync-skills" to push your local skill changes to GitHub.

Frequently Asked Questions about sync-skills

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

FAQPage Schema
How do I synchronize local Claude Code skills with a GitHub repository?

To synchronize local Claude Code skills, you can use a single command that automates stashing, pulling, rebasing, and pushing changes directly to your GitHub repository.

What is the best way to automate pushing local skill changes to a remote repository?

Automating local skill changes to a remote repository is best handled by a single command that checks for staged changes, builds a commit message, pushes the update, and reports the commit hash.

Does the skill synchronization process handle merge conflicts automatically?

The skill synchronization process handles conflicts by stashing local changes, pulling remote updates with a rebase, and then popping the stash to ensure changes merge smoothly.

Can I avoid creating empty commits when syncing my local skills to GitHub?

Yes, you can avoid empty commits during skill synchronization because the process uses conditional checks to verify staged changes and confirms if they actually need to be pushed.

Do I need to manually pull changes on other machines after syncing my skills?

Yes, after syncing skills to GitHub, you need to manually pull changes on other machines because the process only pushes updates and provides a pull reminder to keep repositories current.