Bug lifecycle for Virto Commerce QA — bug filing, autonomous fixing, fix verification, online bug monitoring, self-diagnostics (/vc-self-check), and one renderer for every result comment and report page (/vc-fix:qa-report). Onboarding comes from vc-init (installed with it). Self-contained plugin (10 agents, 16 skills, 7 commands).
16 skills · 7 commands · 10 agents · hooks
PREVIEW — one testing flow per ticket: /vc-test:ticket-context (one gated context bundle, read from Jira or Azure Boards and GitHub or Azure Repos through vc-init's $VC_RUN bridge, or through the host's MCP servers on a host-governed project), /vc-test:qa-test-strategy (floors, gate, an independent verifier), then scenarios that hunt significant bugs, approved at one human point, one agent each, costed per step. /vc-test:init for its own settings. Depends on vc-init and vc-fix. /vc-test:qa-triage-results runs from the plugin; investigation is vc-fix:qa-investigate. /vc-test:qa-design and the ui-ux-expert agent run the visual lane on a Playwright lane the run leaves free.
4 skills · 2 commands · 7 agents
Three-layer performance loop — BenchmarkDotNet A/B (L1), k6 load harness (L2), dotnet-trace allocation/CPU/DB attribution (L3), machine-readable perf-verdict, optimization PRs. Depends on vc-init (onboarding, profile) and vc-fix (routing, backend dev/review agents). Advisory only.
4 skills · 5 commands · 1 agent
Skills for the Virto Commerce storefront (vc-frontend): keep a theme fork up to date with upstream, and add a storefront plugin to a backend module. Can make mistakes: review every change before merging.
3 skills
Onboarding for the Virto Commerce QA plugins — /project-init, the only writer of project-profile.json. Every token it and its dependents need (GitHub, Azure DevOps, Jira) is kept in vc-secrets and reaches a process only through the $VC_RUN bridge, so none sits in a project file. Depends on vc-secrets; Installs on its own; every Virto plugin that reads the profile depends on it.
1 skill · 1 command · hooks