gitly-sync
/gitly-sync
Explain and safely synchronize local work with a Git remote using fetch, fast-forward pull, or non-force push. Use for sync, push, pull, online backup, "back it up", "סנכרן", or "גיבוי בענן".
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Explain and safely synchronize local work with a Git remote using fetch, fast-forward pull, or non-force push. Use for sync, push, pull, online backup, "back it up", "סנכרן", or "גיבוי בענן".
Triggers from the description
Original author description
Explain and safely synchronize local work with a Git remote using fetch, fast-forward pull, or non-force push. Use for sync, push, pull, online backup, "back it up", "סנכרן", or "גיבוי בענן".
How it works
- Responsibility and triggers
- Prerequisites and inspection
- Mutating workflow
- Output, errors, and recovery
SKILL.md preview
--- name: gitly-sync description: Explain and safely synchronize local work with a Git remote using fetch, fast-forward pull, or non-force push. Use for sync, push, pull, online backup, "back it up", "סנכרן", or "גיבוי בענן". license: MIT metadata: collection: vibe.md group: gitly source: https://github.com/vibe-md/vibe.md upstream: https://github.com/NirGeron98/Gitly upstream-commit: fe33bbae13552ed8973c6949b1d21e1ce2b746c9 --- # Gitly sync Read [the shared operating contract](../GITLY.md) first and follow its approval contract. ## Responsibility and triggers Move versions between the local project and a configured remote without overwriting history. Examples: “Back up my project to GitHub,” “get the online changes,” “סנכרן עם גיטהאב”. Use `gitly-github-connect` when authentication or a remote is missing and `gitly-save` when local changes need a version first. ## Prerequisites and inspection Inspect branch/HEAD, status/index, remotes, upstream configuration, and local tracking refs without network access. Explain that remote knowledge may be stale. Network fetch changes remote-tracking refs, so it is a mutation requiring approval. Detect detached HEAD, dirty pull state, missing upstream, ahead/behind counts, divergence, protected branches, submodules, and LFS. ## Mutating workflow Prepare exactly the requested direction: - Refresh knowledge: `git fetch -- <remote>`. - Download updates only when the tree is clean: `git pull --ff-only <remote> <branch>`. Refuse divergence instead of creating a silent merge. - Upload: `git push --set-upstream <remote> <branch>`. Never add force flags. The plan must name remote/branch, data direction, known divergence, credential/helper behavior, remote effect, and recovery. A save approval never authorizes a push. Recheck local state and remote configuration after approval, execute, then fetch/inspect refs as needed to verify the relationship. ## Output, errors, and recovery Report whether local and online versions now match, what moved, and what remains only local/remote. Stop on non-fast-forward rejection, divergence, dirty pull, offline/authentication errors, changed upstream, protected branches, partial network failure, or unexpected remote URLs. Preserve history; inspect again and offer choices instead of force-pushing or auto-merging.
Versions
The database has no other skills named gitly-sync.
Database snapshot: 13.11.2026 · package version be0fd289a9af (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100gitly-setup
Check Git readiness and safely prepare a project repository. Use for Gitly setup, initialization, Git identity, ignore-file, "set up Git", "הגדר גיט", or "אתחל מאגר" requests. - 100gitly-status
Explain whether project work is saved, backed up, current, or at risk using local Git evidence. Use when the user asks what state the project is in or whether work is safe; do not use to test application behavior. - 100git-sync
Sync the current branch in one pass — commit the working tree as one commit per logical change (in the host repo's commit format, or the super-board writing standard), gate Supabase schema changes, merge-pull, resolve conflicts hunk by hunk, then push without force. Use when the… - 100git-sync
Sync the current branch in one pass — commit the working tree as one commit per logical change (in the host repo's commit format, or the super-board writing standard), gate Supabase schema changes, merge-pull, resolve conflicts hunk by hunk, then push without force. Use when the… - 91commit-push
Commit with a Conventional Commits subject, then push. Use for /commit-push, "commit and push", "commit this and push". Must push. Never force-push. - 96git-remote-publishing
Use when preparing a repo's first public push or release.