git-rebase-workflow

A safe git rebase requires branch eligibility checks and adherence to force-with-lease policies. This skill automates local branch rebasing by validating readiness, logging conflicts, and ensuring history cleanup is auditable before merging.

Linearizing feature branch history involves applying rebase readiness checks and documenting conflict resolutions. This skill reorganizes commits under controlled guidelines to ensure history hygiene and safe interruption handling during the workflow.

Conflict-aware rebasing requires documenting resolutions and generating an auditable log. This skill applies conflict resolution during local rebases and records the results using provided safety rules and templates for compliance tracking.

Yes, rebase readiness verification can be automated. This skill checks if a branch can be rebased without violating policy, applying readiness checklists and safety rules to ensure the branch is eligible for history cleanup.

Force-with-lease policies are enforced during automated rebasing to minimize risks from rewritten history. This skill integrates these safety rules to protect local branch history when linearizing commits before integration.

You should avoid rebasing when a branch fails readiness checks or violates safety policies. This skill helps identify these constraints by verifying rebase eligibility and enforcing force-with-lease rules before any history cleanup occurs.