op-config-sync

To sync configuration files across multiple machines using Git, this Skill pulls and pushes changes to a remote repository while running pre-sync validation checks to ensure data integrity. It guides safe commit practices to prevent inconsistencies between environments.

Pre-sync validation is needed before pushing changes to prevent potential errors across your development environments. The Skill runs a doctor.sh script to check for issues, ensuring configuration integrity and preventing sensitive data from being committed.

Yes, you can use this workflow to synchronize OpenCode skills, agents, and commands across multiple PCs. After adding a new configuration element, the Skill pushes those changes to a remote repository so your other machines can pull the latest validated state.

The best way to prevent sensitive data from being committed during config synchronization is using built-in safety checks. This Skill enforces secure commit practices and runs validation scripts to ensure sensitive information is not pushed to the remote repository.

Config synchronization works without external dependencies, relying solely on Git and internal scripts. The Skill operates independently to manage your OpenCode configuration files, requiring only a remote Git repository to facilitate the pull and push actions.

You should not use automated Git synchronization when your local configuration contains unvalidated changes or sensitive data. The Skill addresses this by requiring pre-sync validation to pass, halting the process if the doctor.sh script detects potential environment issues.