git-sync

Stage, commit, and push local workspace changes to a GitHub repository.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of backing up your local workspace changes to a remote GitHub repository, ensuring your work is version-controlled and safe from local data loss.

Core Features & Use Cases

  • Automated Committing: Stages all changes in your workspace.
  • Automated Pushing: Pushes committed changes to the main branch of your remote repository.
  • Safety Checks: Includes checks to prevent committing if there are no changes and utilizes pre-commit hooks to help prevent secret leakage.
  • Use Case: After making significant progress on a feature, you can trigger this skill to ensure all your code is backed up and available on GitHub.

Quick Start

Use the git-sync skill to commit and push your local changes to the remote repository.

Frequently Asked Questions about git-sync

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

FAQPage Schema
How do I automatically sync local changes to a GitHub repository?

To automatically sync local changes to GitHub, this skill stages all workspace modifications, commits them with a provided or default message, and pushes directly to the main branch for routine backups.

Can I automatically push local code changes to the main branch on GitHub?

Yes, you can automatically push local code changes to the main branch on GitHub. The skill stages all modifications and commits them with a default or provided message before pushing.

How does automated git backup prevent accidental secret exposure?

Automated git backup prevents secret exposure by utilizing pre-commit hooks. These safety checks help identify and block sensitive data before changes are committed and pushed to the remote repository.

What happens if I trigger automated git sync with no local changes?

If you trigger automated git sync with no local changes, the process includes safety checks that prevent committing. It stops the operation to avoid creating empty commits on your main branch.

Do I need to manually write commit messages for automated version control backups?

No, you do not need to manually write commit messages for automated version control backups. You can provide a custom message, but the skill automatically applies a default one if omitted.

Is automated git sync suitable for routine version control management?

Yes, automated git sync is designed for routine version control management. It ensures your local workspace modifications are regularly backed up and available on GitHub without manual intervention.