What problem does it solve? Keeping a long-lived session branch current with origin/main requires a careful rebase, deliberate conflict resolution, a safe force-push, and PR metadata updates — a history-rewriting workflow that is error-prone when done ad hoc. ## Core Features & Use Cases - Guided rebase workflow: Fetches origin/main, measures divergence, replays commits with a structured conflict-resolution playbook that pins a source of truth and audits auto-merged files. - Safe history rewriting: Force-pushes only with --force-with-lease after running the verification floor (pnpm run check), and refuses to run on a dirty tree. - PR actualization: Updates the linked GitHub PR title, body, closing-issue reference, and draft status via gh so the PR reflects the rebased branch. - Use Case: After main has moved ahead while you worked on a session branch, run /sync-main to rebase your commits, resolve conflicts against the registry source of truth, verify with pnpm run check, force-push, and refresh the PR. ## Quick Start Ask the agent to run /sync-main to rebase the current session branch onto origin/main and update its linked pull request.