qa-hotfix

Validate merged commits and release verified fixes as controlled hotfix patches.

2|1|Updated May 27, 2025

Search Tags:#github #release #jira #hotfix #cherry-pick #backport #support branch

Ready to run

npx skills add https://github.com/VirtoCommerce/vc-mcp-testing-module --skill qa-hotfix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-hotfix
Source: https://github.com/VirtoCommerce/vc-mcp-testing-module/tree/main/skills/qa-hotfix
Command: npx skills add https://github.com/VirtoCommerce/vc-mcp-testing-module --skill qa-hotfix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents risky manual hotfix releases by guiding teams through verifying fixes, selecting supported release lines, and publishing controlled patches for frozen bundles.

Core Features & Use Cases

Release Validation Workflow: Resolves a task to its pull request and commit, then verifies the fix is merged and already shipped before any backport action.
Controlled Backporting: Checks support branches, prepares cherry-picks, and triggers release workflows with explicit confirmation gates.
Use Case: A release manager needs to deliver an already-released bug fix to stable VirtoCommerce bundles and uses this Skill to validate eligibility and create patch releases safely.

Quick Start

Use the qa-hotfix skill to release the fix for task VCST-XXXX into the required stable bundles after verifying the merged and shipped gates.

Frequently Asked Questions about qa-hotfix

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

FAQPage Schema

How do I safely backport a bug fix to a stable release branch?▼

To safely backport a bug fix, validate that the commit is merged and shipped, verify the support branch exists, prepare the cherry-pick, and trigger the release workflow through explicit confirmation gates.

What is the process for releasing a hotfix patch for frozen VirtoCommerce bundles?▼

Releasing a hotfix patch for frozen bundles requires resolving the JIRA task to its pull request, verifying the fix is already shipped, checking support branch availability, and applying controlled cherry-picks.

How do I cherry-pick a merged commit from a GitHub pull request into a support branch?▼

Cherry-picking a merged commit requires locating the original pull request, confirming the fix is already shipped, verifying the target support branch, and applying the commit through gated write validations.

Why does my hotfix workflow require validation of shipped releases before backporting?▼

Hotfix workflows require validation of shipped releases before backporting to ensure the fix is stable and finalized, preventing risky manual patches from being applied to unverified code.

Can I release a hotfix for a JIRA task that has not been merged or shipped yet?▼

You cannot release a hotfix for an unmerged or unshipped JIRA task. The workflow explicitly requires verifying that the pull request is merged and the release is shipped before allowing any cherry-pick action.