git-find-fork

Git fork point detection identifies the actual merge-base of your branch despite history rewrites. This Skill computes the true divergence point by analyzing branch history, handling rebases and squashes automatically to reveal where your branch truly split from its parent.

Yes. This Skill analyzes your branch and outputs indicators showing whether history has been rewritten through rebases or squashes. It compares the current state against the computed fork point to flag any modifications to the branch timeline.

This Skill automatically computes merge-base across local and remote contexts, even when the parent branch is unclear or the history contains multiple rebases and squashes. It outputs the merge-base alongside commits since fork and rewrite indicators.

Fork point analysis outputs branch name, HEAD, parent branch, merge-base, commit count since divergence, and boolean flags for history rewrites and squashes. This metadata helps you understand your branch's true origin and how it has evolved.

No. This Skill uses Bash scripting and Git commands to compute fork points automatically without manual parent tracking. It handles unknown parents and complex rebase scenarios, eliminating the need to remember or manually specify branch relationships.