rebase-downstream

You can automate a rebase of downstream branches by detecting dependent branches and rebasing them sequentially. This skill handles ordered rebasing, conflict resolution assistance, and preflight checks to ensure code consistency across the branch tree.

Propagating updates to dependent feature branches requires an ordered rebase starting from the closest downstream dependency. This automated workflow detects the dependent tree, resolves conflicts, and runs checks to prevent integration headaches.

Automated branch rebasing handles both linear chains and trees with sibling branches. It intelligently detects all downstream dependencies and rebases each branch in order, maintaining stability across complex branch topologies.

When rebasing a tree of dependent branches, the workflow provides conflict resolution assistance and attempts to resolve merge conflicts automatically. This reduces manual errors during continuous integration and code integration.

During an automated downstream rebase, preflight checks run automated build and test validations on each branch. This ensures stability and code consistency before the rebase process moves to the next downstream dependency.

You should avoid automating a downstream rebase if your branches lack clear dependency mappings or if preflight checks fail, as unresolved merge conflicts can disrupt the ordered rebasing process across the tree.