sync

You are running the /sync workflow — a thin wrapper around the git-safe-sync skill for the common "commit + push to main" path.

Current state

!git status --short --branch

Pending diff (stats)

!git diff --stat !git diff --cached --stat

Recent commits (for tone/style)

!git log --oneline -5

---

Arguments (optional commit subject hint): $ARGUMENTS

Required workflow

Follow the git-safe-sync skill rules strictly. The sequence below is mandatory — do not collapse turns.

1. Research (this turn): summarize what would be committed and propose a commit message. If $ARGUMENTS is non-empty, use it as the subject; otherwise infer a Conventional Commits subject from the diff. Group co-changing files; flag any that look unrelated and should be split.
2. Confirm (this turn): present the user with explicit options via AskUserQuestion: Commit & Push to main, Open a PR instead, Commit only, or Cancel. Do NOT execute any git/gss command yet.
3. Execute (next turn, only after the user picks an option):
   • Stage files by explicit name (never git add -A / git add .).
   • Commit using a HEREDOC message that ends with Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>.
   • For Push: generate the approval token as a separate Bash call (mkdir -p ~/.config/gss && git rev-parse HEAD > ~/.config/gss/approval.token), then run gss push as a second Bash call. Chaining them with && is intentionally blocked by safety_guard.sh. If the pushed branch already has an open PR, gss push updates the branch but NOT the PR body — you MUST then refresh it with gh pr edit <number> --title/--body so the description covers every commit now on the PR (re-derive What/Why/Impact/Testing from git log <base>..HEAD). Leaving a stale description is an incomplete sync.
   • For PR: use the same two-call pattern with gss pr instead of gss push. Per the skill's PR Hygiene rule, you MUST pass a real description — gss pr --title "<subject>" --body "<What/Why/Impact/Testing markdown>". gss pr does not infer a body, so omitting --body ships an empty PR description. (gss pr has no --draft flag; classic PRs are created ready-for-review.)
4. Surface (post-execution): show the commit SHA, the safety backup branch, and the GitHub compare/PR URL. If you pushed to an existing PR, confirm its description was refreshed to match the new scope. Then ask whether to open the URL in the browser — to open it, run the open-url <url> helper (opt/scripts/misc/open-url), which selects the right opener per platform (open on macOS, wslview/explorer.exe under WSL, xdg-open on Linux). If it exits non-zero (e.g. headless session), just leave the link visible.