메뉴
QA cherry-pick tracking documents for polkadot-sdk fork upgrades. Use when auditing, verifying, or updating cherry-pick tables in docs/cherry-picks/, when upgrading to a new polkadot-sdk stable branch, or when checking if a cherry-pick was applied.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Analyzes weight file diffs after benchmarks to flag significant regressions in ref_time, proof_size, and DB reads. Use when updating weights, running benchmarks, or reviewing weight changes.
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when executing implementation plans with independent tasks in the current session
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
| name | qa-cherry-picks |
| description | QA cherry-pick tracking documents for polkadot-sdk fork upgrades. Use when auditing, verifying, or updating cherry-pick tables in docs/cherry-picks/, when upgrading to a new polkadot-sdk stable branch, or when checking if a cherry-pick was applied. |
Moonbeam maintains forks of polkadot-sdk, frontier, evm, ethereum, and moonkit. Each fork has a moonbeam-polkadot-stable<YYMM> branch with cherry-picks on top of the upstream stable release. The cherry-pick tracking documents in docs/cherry-picks/ record every cherry-pick and its status.
Cherry-pick tracking documents live in docs/cherry-picks/ inside the moonbeam repository and follow the naming convention <repo>-stable<YYMM>.md. For example:
docs/cherry-picks/polkadot-sdk-stable2512.md — current stable branchdocs/cherry-picks/polkadot-sdk-stable2506.md — previous stable branchNote: The filenames above are examples. Check the
docs/cherry-picks/directory for the actual documents relevant to the current upgrade cycle.
Each repo section has a markdown table with these columns:
| Column | Description |
|---|---|
| Applied | Yes/No — was it applied on the previous stable branch? |
| Title | Human-readable description of the change |
| Commit | Link to the actual commit on the current moonbeam-polkadot-stable<YYMM> branch (empty if Dropped) |
| Cherry pick | Included (on current branch), Dropped (removed), squash (folded into another) |
| Status | Upstream status: Permanent, Temporary, PR Upstream Merged, Upstream PR not merged, Needs PR upstream, Closed |
| Upstream PR | Link to the upstream PR (if any) |
| Note | Context, Jira tickets, related PRs |
This skill coordinates several activities. Read the relevant resource when performing each task:
| Activity | Resource | Description |
|---|---|---|
| Verify cherry-picks | ./verify-cherry-picks.md | Confirm cherry-picks against a branch using git merge-base |
| Create new document | ./create-cherry-pick-document.md | Build a tracking doc for a new stable branch upgrade |
| Common pitfalls | ./common-pitfalls.md | Known gotchas when working with cherry-pick tables |
For verification and auditing tasks, dispatch the moonbeam-engineering:cherry-pick-specialist agent once per repo so that each fork can be processed in parallel.
moonbeam-engineering:cherry-pick-specialist, providing: