From dev
Trigger the cherry-pick robot to backport a merged PR to a release branch. Checks Target Version from JIRA if no branch is specified.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dev:backport PR_NUMBER [BRANCH]PR_NUMBER [BRANCH]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Backport merged PR #$ARGUMENTS[0] to a release branch.
Backport merged PR #$ARGUMENTS[0] to a release branch.
$ARGUMENTS[0]$ARGUMENTS[1]gh pr view "$ARGUMENTS[0]" --json state,mergedAt,title
The PR must be merged. If not, inform the user and stop.
If $ARGUMENTS[1] is provided, use it as the target branch.
Otherwise, extract the JIRA ticket key from the PR title and check Target Version:
bash .claude/scripts/jira-ops.sh check-version <TICKET-KEY>
Map Target Version to release branch. The mapping is project-specific — consult the project's release branch naming convention. Ask the user if the mapping is ambiguous.
gh pr comment "$ARGUMENTS[0]" --body "${CHERRYPICK_COMMAND:-/cherrypick} <BRANCH>"
Report:
The bot can fail due to merge conflicts or missing labels. When that happens, create the backport manually:
git fetch origin
git checkout -b <BRANCH>-backport-<PR_NUMBER> origin/<BRANCH>
git cherry-pick -m 1 <MERGE_COMMIT_SHA>
If there are conflicts:
git add the resolved filesgit cherry-pick --continueThen push and create the backport PR:
git push -u origin <BRANCH>-backport-<PR_NUMBER>
gh pr create \
--title "[<BRANCH>] <ORIGINAL_PR_TITLE>" \
--body "Backport of #$ARGUMENTS[0]" \
--base <BRANCH>
npx claudepluginhub quay/ai-helpers --plugin devProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.