cherry-pick-portlisted

# Cherry Pick Port ## Core Question Should this commit be cherry-picked or backported to the target branch, and how can it be done safely? ## When To Use Use this skill when: - the user asks to cherry-pick a commit - the user asks to backport a fix to another branch - a release branch needs selected commits from another branch - the user asks whether a patch is already applied ## When Not To Use Do not use this skill when: - syncing a whole branch - applying raw patch files - resolving conflicts after cherry-pick - pushing the result by default Route to: - branch update routes to `sync-branch` - conflicts route to `resolve-conflicts` - abort/recovery routes to `undo-recover` - push routes to `branch-workflow` ## Required Evidence Before action, inspect or establish: - source commit SHA and diff - target branch and current state - clean target worktree - duplicate detection such as patch-id or equivalent diff evidence - project backport policy including `-x` if available - tests relevant to the change No-evidence rule: - Do not make strong claims without observed evidence. - State assumptions when proceeding under incomplete evidence. - Stop when missing evidence affects safety, correctness, user work, remote state, or irreversible action. ## Operating Contract You MAY: - inspect relevant repository state and project files. - generate a plan, report, or local artifact within the declared risk scope. - route to another skill when the requested action is outsid