Skip to content

Claude Skills by VirtoCommerce

github.com/VirtoCommerce

65 skillsA× 62B× 30 installs75 views

Perf LoadtestARun the L2 k6 load harness against the live Aspire-hosted backend and produce a summary + optional dotnet-counters CSV. Use to answer "how does the running system behave under load" — throughput, p95 latency, GC pressure — as opposed to L1 (BenchmarkDotNet, code-level) or L3 (dotnet-trace, attribution).developmentgoshellVotes: 0GitHub stars: 2
Perf LoopAOrchestrates the three-layer performance loop (bench → load → diagnose → optimize → verify) on the local Aspire-hosted backend. Use when the user asks to "run the perf loop", "load test X", "profile the backend", "where do the allocations come from", "why is this operation slow", or to verify a performance fix end-to-end. Routes to the right layer and tool; does not duplicate them. For pure BenchmarkDotNet before/after comparison use `perf-benchmark` directly.researchrustgoVotes: 0GitHub stars: 2
Perf TraceACapture a dotnet-trace / dotnet-counters session against the live backend and parse it with perftools (allocparse/cpuparse/dbparse) to attribute WHO is responsible for what L2 observed. Use when you know load behaves a certain way (L2) and need to find the responsible code — allocation churn, on-CPU time, or DB command shape.toolsgoshellVotes: 0GitHub stars: 2
Kb ReportA[KB] Read the knowledge base's own logs and render the report — what agents asked, what the base could not answer, which answers were useless, and the §15 acceptance verdict. Run it before deciding what to build for the base next, and to judge a check wave.testinggoshellVotes: 0GitHub stars: 2
Prompt ReviewAUse when asked to review, check, heal or improve a prompt file in this repo — a skill (SKILL.md and its supporting files), a command or an agent definition under .claude/ or plugins/*/ (\"review the qa-test skill\", \"is this agent prompt any good\", \"fix the prompts changed on this branch\"). Not for test cases (/qa-review-tests), oracles (/qa-review-oracles), product or script code (/code-review), a skill's runtime telemetry (/vc-self-check), or authoring a brand-new skill (anthropic-skill...ai-agentsgobashVotes: 0GitHub stars: 2
Qa Test Data ModelA[QA Method] Build, update or audit a TEST DATA MODEL — the declared data STATE each behaviour of a domain requires (entity, required state, lifecycle scope, acquisition strategy, the existing seeder and @td() alias that reach it, cleanup, what the data discriminates) at test-data/models/<name>.data-model.json, plus executable profiles per mind-map node. Answers 'what state must exist before this runs?', never 'which API calls create it' — the existing seeders stay the executors. Hands a profi...developmentgonodeVotes: 0GitHub stars: 2
Qa Test FastA[Testing] Methodology behind the /qa-test-fast command — the grounded quick ticket test between /qa-test FAST and FULL. Use when running or changing /qa-test-fast, or when deciding whether a ticket fits it.researchgonodeVotes: 0GitHub stars: 2
Qa Test Mind MapA[QA Method] Build, update or audit a TEST MIND MAP — the machine-readable behaviour graph of one domain (behaviours, branches, states, transitions, the data each needs and produces, evidence per node) at .claude/knowledge/domain/<name>.mind-map.json. Answers 'how can this domain behave?' between the domain map ('what exists') and the suite CSVs ('how is a path executed'); cases link to it through Behavior: stamps. Not an oracle, not a case generator.researchgonodeVotes: 0GitHub stars: 2
Qa Test ModelA[QA Method] Use when a ticket needs a TEST MODEL (the fault model: value chain, mechanism matrix, scenario table) — /qa-test FULL Step 1e, /qa-test-fast Stage 1, or before /qa-checklist --from-model or /qa-exploratory ticket, which both need a model to exist. Builds or amends reports/ba/test-models/<TICKET>-<date>.md. Not for test cases (/qa-test-cases-generator) or a domain's behaviour graph (/qa-test-mind-map).businessnodeVotes: 0GitHub stars: 2
Qa Env UpgradeA[QA Methodology] Bring a deployed environment up to the latest released modules + platform and the newest green dev alpha of the storefront theme, as ONE deploy PR on vc-deploy-dev that a human merges. Use when asked to bring an env up to date / 'обновить стенд до последних релизов'. Not for hotfix delivery (/qa-hotfix-check) or a ticket's PR builds (/qa-deploy-pr). Read-only until the operator's yes; never merges.developmentgobashVotes: 0GitHub stars: 2
PlansA> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking. **Goal:** Replace the draft `/qa-env-upgrade` command with a skill backed by a deterministic script. The script comes from renaming and extending `scripts/deploy/deploy-pr-artifact.ts`. **Architecture:** - **Script.** `deploy-pr-artifact.ts` becomes `scripts/deploy/vc-deplo...developmenttypescriptgoVotes: 0GitHub stars: 2
PlansA> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking. **Goal:** Add a `qa-report` skill that turns any finished run (`/qa-test`, `/qa-test-fast`, `/qa-verify-fix`, `/qa-regression`, `/qa-smoke`) into **one** brief, char-budgeted tracker comment and **one** human-readable HTML page. Every template lives in one folder, and the f...testinggoshellVotes: 0GitHub stars: 2
DoctorARun the vc-secrets diagnostic and interpret it — which declarations loaded, which secrets resolve, which need migrating, and what to do about each FAIL. Use when a wrapped MCP server shows failed, or after any change to a declaration.toolsrustgoVotes: 0GitHub stars: 2
InstallAPut the vc-secrets shim at a stable path and print the settings entry plus the literal commands that use it. Run once per machine. NOT needed after an ordinary plugin update — the shim resolves the plugin's current location by itself.toolsrustshellVotes: 0GitHub stars: 2
MigrateAOne-time: move user-scope secrets stored under the older flat `mcpw:` key prefix to their namespaced keys. A repository's local-store secret is skipped. Needed only on a machine that used the launcher this plugin replaces — otherwise every user-scope local-store secret not already set reports `no legacy entry`. Idempotent.toolsrustshellVotes: 0GitHub stars: 2