git-sync

What This Skill Does

The git-sync skill serves as an automated bridge between your local development workspace and your remote GitHub repository. It streamlines the version control workflow by encapsulating the standard git triad—adding all modified files, committing them with a contextual message, and pushing the changes to the origin. By automating these repetitive administrative tasks, the skill ensures that your codebase is consistently backed up and synchronized with your remote environment, reducing the risk of data loss and facilitating easier collaboration across multiple machines.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/autogame-17/git-sync

Ensure that you have your GitHub authentication configured (SSH keys or personal access tokens) within your local environment before running the installation, as the tool relies on your system's git credentials to authorize the push operation.

Use Cases

This skill is ideal for developers who want to focus on logic rather than version control mechanics. Key use cases include:

• Automated Backup: Triggering the skill after every major code block completion to ensure no progress is lost.
• PCEC Cycles: Integrating the skill into your Proactive Continuous Evolution Cycle (PCEC) to maintain a live history of every iteration performed by the AI agent.
• End-of-Session Cleanup: Using the skill as a final command before closing your development session to guarantee the remote repository reflects your latest work.

Example Prompts

1. "I have finished the current module, please run git-sync and use the message 'Complete refactor of authentication logic'."
2. "Sync my recent changes to GitHub; standard auto-sync message is fine."
3. "After you finish implementing the UI updates, go ahead and git-sync the workspace so I can view it on the repo."

Tips & Limitations

• Safety First: The skill is hard-coded to respect .gitignore files and utilizes pre-commit hooks, ensuring that you don't accidentally push sensitive environment variables or secrets to a public or private repository.
• Pre-requisites: The repository must already be initialized as a git project; the skill acts as a helper, not a replacement for manual repository initialization.
• Commit Messages: While a default message is provided, providing specific messages is highly encouraged to maintain a searchable and readable commit history, which is vital for long-term project maintenance.