qa-bundle-check

Compare pinned VirtoCommerce bundle versions against available same-line patch releases.

2|1|Updated May 27, 2025
One-click install
npx skills add https://github.com/VirtoCommerce/vc-mcp-testing-module --skill qa-bundle-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-bundle-check
Source: https://github.com/VirtoCommerce/vc-mcp-testing-module/tree/main/skills/qa-bundle-check
Command: npx skills add https://github.com/VirtoCommerce/vc-mcp-testing-module --skill qa-bundle-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents teams from manually checking stable VirtoCommerce bundle versions by identifying missing same-line patch hotfixes while avoiding false alarms from newer minor releases.

Core Features & Use Cases

  • Bundle Version Auditing: Compares pinned module, Platform, and Theme versions against available patch releases on the same major.minor version line.
  • Automated Release Traceability: Finds release provenance through GitHub releases, pull requests, and related JIRA task keys when hotfixes are detected.
  • CI and Maintenance Workflows: Helps QA and release teams verify whether stable bundles are ready for deployment or require patch updates.

Quick Start

Run the qa-bundle-check skill to verify whether a VirtoCommerce stable bundle has available hotfix updates.

Frequently Asked Questions about qa-bundle-check

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

FAQPage Schema
How do I check VirtoCommerce bundles for missing hotfixes?

To check VirtoCommerce bundles for missing hotfixes, run the qa-bundle-check skill which compares pinned stable versions against available patch releases on the same major.minor version line. It identifies missing same-line hotfixes while avoiding false alarms from newer minor releases.

What is a bundle version audit for VirtoCommerce modules?

A bundle version audit for VirtoCommerce modules is the process of comparing pinned module, Platform, and Theme versions against available patch releases. This ensures stable bundles include all required hotfix updates before deployment, preventing teams from manually checking versions.

How does hotfix detection work for VirtoCommerce GitHub releases?

Hotfix detection for VirtoCommerce GitHub releases works by applying deterministic version parsing to compare pinned bundle versions against available patches on the same major.minor line. It inspects GitHub releases and optionally extracts pull requests and JIRA task keys for provenance.

Can I automate VirtoCommerce release preparation and CI gating with patch version checking?

Yes, you can automate VirtoCommerce release preparation and CI gating with patch version checking. The skill validates whether stable bundles require patch updates, making it suitable for QA validation, release workflows, and maintenance audits of VirtoCommerce modules.

Does bundle audit check for newer minor releases or only same-line patch hotfixes?

Bundle audit checks only for same-line patch hotfixes, intentionally avoiding false alarms from newer minor releases. It applies deterministic version parsing to strictly compare pinned versions against available patch releases within the exact same major.minor version line.

Why does my VirtoCommerce stable bundle show a missing hotfix during QA validation?

Your VirtoCommerce stable bundle shows a missing hotfix during QA validation because a patch release exists on the same major.minor version line that is not pinned in your current bundle. The skill detects this by comparing your versions against available GitHub releases.