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.
Plugin vc-perf from marketplace ai-tools in VirtoCommerce/ai-tools. Commands read from the repo's manifest — 2 days ago.
perf-benchmarkRun VirtoCommerce x-module BenchmarkDotNet suites (the XAPI targets configured in perf.benchmark.xapiTargets) and turn two runs into a machine-readable performance verdict. Use to check whether a change regressed allocations or time across two revisions of this module's own source, between this modu
perf-loadtestRun 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, attributi
perf-loopOrchestrates 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 perf
perf-traceCapture 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
/vc-perf:perf-benchmarkL1 BenchmarkDotNet before/after — did my code's allocation/time envelope regress? Runs a scoped A/B (own before/after, own vs upstream, or upstream before/after) and emits the machine-readable perf-verdict. Thin command over the perf-benchmark skill.
/vc-perf:perf-fixOptimization lifecycle for a Virto Commerce performance finding: diagnose → rank candidates → implement the minimal change → re-measure to a verdict → route → review → open PR. The perf analog of /qa-fix. Reuses vc-fix's developer/reviewer/routing agents (never duplicates them). Advisory; single rep
/vc-perf:perf-initOnboard vc-perf onto a deployment — reuse vc-init's /project-init, then add the perf block to project-profile.json (through vc-init's profile-set.mjs) and install perf prerequisites.
/vc-perf:perf-loopDiagnose why an operation is slow or where its allocations/CPU/DB time come from — the L2 (load) + L3 (attribution) entry point. Routes to the right layer/tool and ends with ranked optimization candidates. Thin command over the perf-loop skill.
/vc-perf:perf-verifyRe-measure an operation after a change and emit a pass/fail verdict — the perf 'green'. Re-runs the same layer(s) with IDENTICAL knobs as the baseline and reports whether the finding improved (verdict improved / responsible frame gone / p95 down) or not. Used by /perf-fix step 4 and standalone.
perf-analystPerformance attribution analyst for Virto Commerce. Reads the loop's measurement artifacts — the L1 perf-verdict JSON, the L2 k6 summary + dotnet-counters CSV, and the L3 trace-parser attribution — cross-references the VC-specific antipattern catalog, and produces a RANKED list of optimization candi
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
Runs a declared process with its secrets resolved at launch, so no plaintext token sits in an MCP config, a settings env block or a .env file.
3 skills · hooks
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
Harness-native ECC operator layer - 71 agents, 314 skills, 98 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
200 skills · 98 commands · 71 agents · 1 MCP server · hooks
agentic-flow (external: maintained in ruvnet/agentic-flow, pinned to commit d19737b, plugin 3.4.0): the agentic-flow MCP server pinned to [email protected] (ReasoningBank learning, ecosystem tools prompt_injection_scan, swarm_partition_tasks, sublinear_solve, sublinear_pagerank and ecosystem_status, multi-provider routing, autopilot learning; readonly profile by default, no tool pre-approved), 2 agents, 4 skills, /agentic-flow-status, and a mod guard on agentic_flow_agent with /agentic-flow-guard
4 skills · 1 command · 2 agents · 1 MCP server
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
8 skills · 1 MCP server
Perform AI code review on Git diffs — supports workspace changes, branch ranges, and single commits with concurrent per-file analysis, codebase search, and deep context-aware review.
2 commands
Transform Claude into an Azure expert. This plugin integrates the Azure MCP server and specialized Azure skills to move beyond generic advice. It enables Claude to perform real-world tasks: listing resources, validating deployments, diagnosing infrastructure issues, and optimizing costs across 50+ Azure services.
44 skills · 1 MCP server
Systems programming with Rust, Go, C, and C++ for performance-critical and low-level development
3 skills · 1 command · 4 agents
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.