EricTechPro/super-board / skills/git-sync
git-sync
VerifiedSync 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 user runs /git-sync or says "git-sync", "sync", "commit and push", "pull and push", or "sync my branch".
README.md
View on GitHub# /git-sync
Commits the working tree, pulls and pushes the current branch in one pass, then says what it did.
## What It Does
- **One change, one commit.** Groups the diff into logical changes and stages each by path. Never `git add -A`.
- **Writes the host's commit format** when the repo's `AGENTS.md`, `CLAUDE.md` or `CONTRIBUTING.md` defines one; otherwise the super-board [writing standard](../super-board/references/writing-standard.md).
- **Refuses secrets.** A `.env*`, key or credential file stops the run with a warning.
- **Gates Supabase changes.** Schema edits need a migration file; advisors and `migration list --local` run when the CLI is up. Defers to the `supabase` skill when it is installed.
- **Merges, never rebases.** `git pull --no-rebase`; conflicts are resolved hunk by hunk, then the host's fast checks run before the merge is concluded.
- **Pushes safely.** No force push. The default or a protected branch needs your yes; otherwise it offers a PR.
## When To Use It
- At the end of a piece of work, to get it committed and onto the remote.
- When your branch is behind and you want it caught up and pushed.
## Install
Ships in the super-board pack as a secondary skill. `install.sh` copies `skills/git-sync/` to `.claude/skills/git-sync/`. Needs `git`; uses `gh` and the Supabase CLI when present.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |