cross-branch-fix-porter

To port a bugfix when cherry-pick fails, extract the fix intent from the original commit and re-implement it in the target codebase. This analyzes the root cause, maps corresponding files, and generates a migration report for confirmation before applying changes.

Applying a patch across incompatible repositories requires intent analysis rather than direct copy. This process translates the fix intent and produces an adapted patch that conforms to the target project's dependencies, utilities, and coding conventions.

Cross-branch code migration is needed when repositories have incompatible structures, framework differences, or dependency mismatches. When a logical fix must be re-implemented in the target project's code rather than copied verbatim, intent-based porting prevents incorrect adaptations.

Cross-branch porting decides between direct file copy and guided re-implementation. Direct copy is used for safe new files, while guided re-implementation applies the fix intent using the target branch's patterns to ensure minimal, style-consistent changes.

Intent analysis works by examining commit diffs or conversation context to summarize the root cause, scope, and core behavioral change of a fix. It maps original files to corresponding target files and highlights missing or incompatible dependencies before patching.

Porting fixes across incompatible structures requires user confirmation before modifying files. The migration report identifies items needing manual review and highlights missing dependencies, meaning automated application is constrained by the target codebase's structural compatibility.