cherry-pick-followup

To automate git cherry-pick across branches, you can instruct the agent to apply specific commit hashes into the current working tree. This automatically propagates changes to keep documentation and configuration files synchronized.

The best way to synchronize documentation updates is using automated cherry-pick operations to port specific commits. This prevents manual reauthoring and maintains consistency across secondary worktrees without merge overhead.

Yes, you can apply a global policy change to secondary git worktrees by targeting the specific commit. The skill uses standard git CLI access to transfer the changes and verify commit integrity across different branches.

When porting commits between branches, the skill provides a structured path for handling merge conflicts during the transfer process. It guides the agent through resolving conflicts while applying the cherry-pick operations.

Yes, you need standard git CLI access to perform automated cherry-picks. The skill requires command-line tools to execute the operations and verify commit integrity within your git-based repositories.