Git Full-Platform Sync Publisher

Problem

git-sync addresses version and content consistency issues in skill/agent publishing: local directories, _meta.json, SKILL.md frontmatter, changelog, repository README, ZIP artifacts, and targets such as ClawHub, SkillHub, and PyPI can drift apart. When publishing is done with multiple manual commands, mismatches, leaked sensitive data, and packaging gaps are harder to catch early.

How it works

• Multi-target sync: pushes a skill or agent to Gitee and GitHub, and can publish to ClawHub, SkillHub, or PyPI as needed.
• Automatic type detection: identifies skills from _meta.json and agents from __version__ in __init__.py, then routes them to the appropriate publish path.
• LLM handoff decisions: file filtering and sensitive-data redaction write a resume state and exit with code 3; the caller writes the decision file and reruns the same command, avoiding long in-process polling.
• Resumable flow: resume_{name}.json records whether the workflow stopped at file_filter or sensitive_scan, so a rerun skips completed steps and continues from the current phase.
• Unified path and repository management: _paths.py centralizes paths, the repos registry in config.json defines target repositories, and manifest.json records sync state.
• Pre-publish checks: version consistency checks, SKILL.md audit, ZIP packaging, and HTML index generation reduce issues that would otherwise appear after release.

Boundaries

Use it for explicit sync, upload, publish, packaging, or release intents, not as a replacement for generic git commit or git push. It does not resolve git merge conflicts automatically; conflicts require manual handling. Multi-platform publishing depends on network access and valid credentials, and ClawHub, SkillHub, and PyPI have different requirements for version parameters, path formats, and build behavior.