qa-cherry-picks

Update cherry-pick tracking tables in docs/cherry-picks for Moonbeam fork upgrades.

3|2|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Moonsong-Labs/knowledge-work-plugins --skill qa-cherry-picks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-cherry-picks
Source: https://github.com/Moonsong-Labs/knowledge-work-plugins/tree/main/moonbeam-engineering/skills/qa-cherry-picks
Command: npx skills add https://github.com/Moonsong-Labs/knowledge-work-plugins --skill qa-cherry-picks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA cherry-pick tracking documents help maintain audit trails for polkadot-sdk forks during upgrades, enabling verification and updates to cherry-pick tables in docs/cherry-picks/.

Core Features & Use Cases

  • Maintain per-repo tracking documents under docs/cherry-picks/ for current upgrades.
  • Verify cherry-picks against upstream stable branches and update statuses as needed.
  • Create new tracking documents for new stable branches and coordinate review workflows.

Quick Start

Identify the current upgrade's tracking document in docs/cherry-picks/ and update its table to reflect the latest cherry-pick status.

Frequently Asked Questions about qa-cherry-picks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track cherry-picks for Moonbeam fork upgrades against the polkadot-sdk?

To track cherry-picks for Moonbeam fork upgrades, identify the current upgrade's tracking document in docs/cherry-picks/ and update its table to reflect the latest applied statuses and upstream PR links.

What is a cherry-pick tracking document used for in a polkadot-sdk fork?

A cherry-pick tracking document maintains an audit trail for polkadot-sdk forks during upgrades, enabling verification of applied statuses and tracking upstream PR links within per-repo documentation.

How do I create new cherry-pick tracking documents for a new stable branch upgrade?

You can create new cherry-pick tracking documents for new stable branches by coordinating review workflows and generating per-repo files in docs/cherry-picks/ that map upstream PR links and current cherry-pick statuses.

How do I verify cherry-picks against upstream stable branches?

To verify cherry-picks against upstream stable branches, review the tracking document in docs/cherry-picks/ and update the table to ensure statuses accurately reflect the upstream PR links and clear notes.

Can I use this cherry-pick tracking process for repositories other than polkadot-sdk?

Yes, this process coordinates cherry-pick tracking and auditing across polkadot-sdk and related repositories, allowing you to maintain per-repo tracking documents for any Moonbeam fork upgrade.