rebase-advisor

To coordinate a team-wide git rebase after a release, you need a guided workflow that syncs remote changes, stashes local work, rebases branches onto updated develop/main, and auto-merges PRs when CI passes. This ensures all team branches stay aligned with the latest release state.

A multi-branch rebase is needed when your develop or main branch falls behind after a release, and multiple worktrees hold unmerged changes. This scenario requires synchronizing all active branches to prevent integration conflicts and ensure consolidated PRs merge cleanly.

Automating branch management after rebasing requires an end-to-end protocol that performs remote syncs, rebases all active branches, and auto-merges PRs when CI is green. This workflow concludes with post-merge checks and health reporting to verify branch synchronization.

Yes, the guided rebase workflow handles stashing changes before rebasing and generates post-merge health reporting. It covers the full end-to-end protocol including remote sync, rebasing all branches, auto-merges, and validation checks to ensure team-wide branch synchronization.

To start a team sync rebase for a specific repository, describe your multi-branch release scenario to trigger the guided workflow, then initiate the process with the canonical command format /make-no-mistakes:rebase {repo-name} to begin syncing branches across your team.