mirror of
https://github.com/Comfy-Org/ComfyUI_frontend.git
synced 2026-04-30 11:11:53 +00:00
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>
2.8 KiB
2.8 KiB
Logging & Session Reports
During Execution
Maintain execution-log.md with per-branch tables:
| PR# | Title | Status | Backport PR | Notes |
| ----- | ----- | --------------------------------- | ----------- | ------- |
| #XXXX | Title | ✅ Merged / ⏭️ Skip / ⏸️ Deferred | #YYYY | Details |
Wave Verification Log
Track verification results per wave:
## Wave N Verification — TARGET_BRANCH
- PRs merged: #A, #B, #C
- Typecheck: ✅ Pass / ❌ Fail
- Issues found: (if any)
- Human review needed: (list any non-trivial conflict resolutions)
Session Report Template
# Backport Session Report
## Summary
| Branch | Candidates | Merged | Skipped | Deferred | Rate |
| ------ | ---------- | ------ | ------- | -------- | ---- |
## Deferred Items (Needs Human)
| PR# | Title | Branch | Issue |
## Conflict Resolutions Requiring Review
| PR# | Branch | Conflict Type | Resolution Summary |
## Automation Performance
| Metric | Value |
| --------------------------- | ----- |
| Auto success rate | X% |
| Manual resolution rate | X% |
| Overall clean rate | X% |
| Wave verification pass rate | X% |
## Process Recommendations
- Were there clusters of related PRs that should have been backported together?
- Any PRs that should have been backported sooner (continuous backporting candidates)?
- Feature branches that need tracking for future sessions?
Final Deliverable: Visual Summary
At session end, generate a mermaid diagram showing all backported PRs organized by target branch and category (MUST/SHOULD), plus a summary table. Present this to the user as the final output.
graph TD
subgraph branch1["☁️ cloud/X.XX — N PRs"]
C1["#XXXX title"]
C2["#XXXX title"]
end
subgraph branch2must["🔴 core/X.XX MUST — N PRs"]
M1["#XXXX title"]
end
subgraph branch2should["🟡 core/X.XX SHOULD — N PRs"]
S1["#XXXX-#XXXX N auto-merged"]
S2["#XXXX-#XXXX N manual picks"]
end
classDef cloudStyle fill:#1a3a5c,stroke:#4da6ff,color:#e0f0ff
classDef coreStyle fill:#1a4a2e,stroke:#4dff88,color:#e0ffe8
classDef mustStyle fill:#5c1a1a,stroke:#ff4d4d,color:#ffe0e0
classDef shouldStyle fill:#4a3a1a,stroke:#ffcc4d,color:#fff5e0
Use the mermaid tool to render this diagram and present it alongside the summary table as the session's final deliverable.
Files to Track
candidate_list.md— all candidates per branchdecisions.md— MUST/SHOULD/SKIP with rationalewave-plan.md— execution orderexecution-log.md— real-time statusbackport-session-report.md— final summary
All in ~/temp/backport-session/.