Files
ComfyUI_frontend/.claude/skills/backport-management/reference/discovery.md
Christian Byrne 37c6ddfcd9 chore: add backport-management agent skill (#9619)
Adds a reusable agent skill for managing cherry-pick backports across
stable release branches.

## What
Agent skill at `.claude/skills/backport-management/` with routing-table
SKILL.md + 4 reference files (discovery, analysis, execution, logging).

## Why
Codifies lessons from backporting 57 PRs across cloud/1.41, core/1.41,
and core/1.40. Makes future backport sessions faster and less
error-prone.

## Key learnings baked in
- Cloud-only PRs must not be backported to `core/*` branches (wasted
effort)
- Wave verification (`pnpm typecheck`) between batches to catch breakage
early
- Human review required for non-trivial conflict resolutions before
admin-merge
- MUST vs SHOULD decision guide with clear criteria
- Continuous backporting preference over bulk sessions
- Mermaid diagram as final session deliverable
- Conflict triage table (never skip based on file count alone)
- `gh api` for labels instead of `gh pr edit` (Projects Classic
deprecation)

┆Issue is synchronized with this [Notion
page](https://www.notion.so/PR-9619-chore-add-backport-management-agent-skill-31d6d73d3650815b9808c3916b8e3343)
by [Unito](https://www.unito.io)

---------

Co-authored-by: GitHub Action <action@github.com>
2026-03-12 04:55:01 -07:00

1.0 KiB

Discovery — Candidate Collection

Source 1: Slack Backport-Checker Bot

Use slackdump skill to export #frontend-releases channel (C09K9TPU2G7):

slackdump export -o ~/slack-exports/frontend-releases.zip C09K9TPU2G7

Parse bot messages for PRs flagged "Might need backport" per release version.

Source 2: Git Log Gap Analysis

# Count gap
git log --oneline origin/TARGET..origin/main | wc -l

# List gap commits
git log --oneline origin/TARGET..origin/main

# Check if a PR is already on target
git log --oneline origin/TARGET --grep="#PR_NUMBER"

# Check for existing backport PRs
gh pr list --base TARGET --state all --search "backport PR_NUMBER"

Source 3: GitHub PR Details

# Get merge commit SHA
gh pr view $PR --json mergeCommit,title --jq '"Title: \(.title)\nMerge: \(.mergeCommit.oid)"'

# Get files changed
gh pr view $PR --json files --jq '.files[].path'

Output: candidate_list.md

Table per target branch: | PR# | Title | Category | Flagged by Bot? | Decision |