Favicon of cherry-pick-to-release

cherry-pick-to-release Skill

AI Agent SkillCOpen source

Cherry-pick a merged main-branch PR onto a MsQuic release branch (release/X.Y). Published by microsoft in msquic.

What is cherry-pick-to-release Skill?

Cherry-pick a merged main-branch PR onto a MsQuic release branch (release/X.Y). Published by microsoft in msquic. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.

Trust signal
95/100
Maintenance signal
90/100
Adoption signal
91/100

Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.

Key capabilities

  • Includes SKILL.md support
  • Reusable instructions support
  • Developers using msquic

Technical details

Copy skill directory
  • Install or run with Copy skill directory

When to use cherry-pick-to-release Skill

  • Use it for developers using msquic.

Built with

CCopy skill directory

Editorial notes

Source

  • Creator: microsoft
  • Repository: microsoft/msquic
  • Skill file: .github/skills/cherry-pick-to-release/SKILL.md

What it does

Cherry-pick a merged main-branch PR onto a MsQuic release branch (release/X.Y).

Skill instructions

Cherry-Pick to MsQuic Release Branch You are helping a maintainer back-port a fix from main to one or more MsQuic release branches (release/2.4, release/2.5, etc.). This skill encodes the patterns the project uses. When This Skill Activates The user asks to cherry-pick / back-port / "CP" a PR or commit from main onto a release branch. Typical requests: - "Cherry-pick 5942 to release/2.4 and release/2.5" - "Back-port the ACK underflow fix to 2.5" - "CP this commit to the 2.4 release branch" Inputs You Need Before doing anything, make sure you know: 1. Source: a PR number on main (preferred) or a commit SHA on origin/main. 2. Target release branch(es): e.g. release/2.4, release/2.5. If the user is ambiguous (e.g. "to the release branches"), ask whether they want one branch or both, and which. 3. Whether to push / open a PR. You must never push a branch or open a PR without explicit permission. Stop and ask before any git push or gh pr create. If anything is missing, ask before proceeding

Explore related resources

Frequently asked questions

What is cherry-pick-to-release?

cherry-pick-to-release is a open-source AI agent skill with Copy skill directory. Cherry-pick a merged main-branch PR onto a MsQuic release branch (release/X.Y).

Who is cherry-pick-to-release best for?

cherry-pick-to-release is best for reusing agent instructions, scripts, and references.

How do I install cherry-pick-to-release?

Install or run cherry-pick-to-release using Copy skill directory. Check cherry-pick-to-release for the latest setup command.

Is cherry-pick-to-release actively maintained?

cherry-pick-to-release may need a closer maintenance check before production use.

Share:

Stars
4,733
Forks
676
Last commit
9 days ago
Repository age
7 years
License
MIT

Auto-fetched from GitHub.

Ad
Favicon

 

  
 

Similar to cherry-pick-to-release

cherry-pick-to-release: Install, Config & GitHub Signals – SkillIndex