cxavireh/hotz-skills/sync-paper

Synchronize a Paper Repository

Resolve the requested paper directory, parent repository if it is a submodule, and the intended destination from the user's request and existing project configuration. Inspect status, diffs, staged changes, branch, and remotes. Treat 'sync' according to that established destination; if it leaves materially different remote targets possible, ask about the target before sending data.

Commit only the files belonging to this synchronization. Review explicit file paths or selected hunks, and inspect the complete staged diff before committing. Never use git add -A or a blanket path as a shortcut. Preserve unrelated user changes and any unrelated staged content; do not silently include or unstage it. If the index cannot represent the intended commit safely, stop to resolve that specific overlap rather than sweeping the repository into one commit.

When a submodule pointer update is requested or clearly part of the established sync, commit the paper first, then stage only that gitlink in the parent. Do not make the parent commit until its staged diff contains only the intended change.

Push only to the destination and branch authorized by the request. The existence of origin or overleaf does not authorize pushing to it. Use an explicit remote and refspec, respect protected branches, and never force push as part of this workflow. A rejected push requires inspection, not automatic overwrite/rebase.

Verify local commit IDs and the target remote ref for a performed push. Report which files/commits and remote were synchronized, plus anything left pending. Local-only commit requests end after the requested local work.