Git Cherry-pick

Apply only the requested commits onto a branch without merging unrelated changes. This skill is repository- and hosting-provider-agnostic.

Rules

Never assume branch names, ticket prefixes, sites, environments, or hosting providers.
Infer missing values from the user request, repository instructions, branch history, and existing MR/PR context.
Do not ask the user to fill out a form. Show one inferred plan and ask only when ambiguity changes the result.
Create the working branch from the target branch, never from the source branch.
Cherry-pick commits oldest-first with git cherry-pick -x.
Preserve unrelated local changes; use a temporary worktree when needed.
Never modify environment files, secrets, certificates, private keys, or generated local backups.
Do not force-push, rewrite published history, or merge directly into a protected branch without explicit permission.

Classify the request: