Use when implementing features, fixing bugs (including P0 hotfixes and production incidents), refactoring, removing dead code, or deleting legacy paths. Use when user mentions TDD, red-green-refactor, test-first, or when tempted to write code before tests. Use when fixing any bug — even trivial ones. Use when…
Analyze Sui Move test coverage, identify untested code, write missing tests, and perform security audits. Includes Python tools for parsing coverage output and generating reports.
Produces practical, risk-based testing guidance and minimal test plans for features or changes. Use when user asks what to test, how to pick test cases (boundaries, permissions, state machines), how to improve weak tests, or to review existing tests. Covers equivalence partitions, boundary values, decision tables, and…
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
Implements enterprise-grade testing strategies for .NET applications using xUnit, Moq, FluentAssertions, and WebApplicationFactory. Use when writing unit tests, integration tests, or API tests in .NET or C#, configuring test projects, deciding what to mock vs what to test with real dependencies, setting up shared test…
Sauce Labs VDC capability authoring skill for desktop and virtual devices. Use when asked to generate or validate W3C/Appium capabilities for Sauce Labs.
Audit steam-games-mcp — build/test/lint gate, live MCP tool edge-case sweep (input validation, SteamID64/vanity/appid edge cases, key-gating), and source-level code review. Use when asked to test/audit the published or just-fixed steam-games-mcp package, hunt for bugs/edge cases, or repeat "the same kind of testing as…
Quality harness for design-dna Phase 3 output with browser-based visual verification. After an agent generates a design from a Design DNA JSON + user content, this skill acts as a verification and scoring layer — collecting all page resources via console/network inspection, performing section-by-section screenshot…
Operator guide for MCPLab config authoring, Test Case Assistant workflows, execution, and result analysis. Use when users need to create or refine test cases from runs/traces, suggest deterministic checks or value capture, write or debug MCPLab eval YAML, run or queue evaluations, troubleshoot failures, or compare…
Set up the skills-evals library in a repository — discover agent artifacts, interview the user about what to test, scaffold eval cases, and wire CI and local runners. Use when the user wants to set up skills-evals, test their agent skills, add evals for skills or custom agents, check why a skill isn't triggering, or…
Use this skill whenever asked to join an autoevolve run, evolve code toward a measured target, work an evolution population, mutate a candidate under EVOLVE-BLOCK rules, or report measured autoevolve progress and artifacts.
Use when you need lightweight browser QA for a web page, local HTML file, or app: inspect console errors, broken assets, keyboard/focus behavior, viewport readability, and publish evidence-backed findings JSON through a local HTML report viewer.
Run Chisel test-impact analysis on any git project — which tests to run after a change, what's risky, what's untested. Use when the user asks to run chisel, find impacted tests, check risk or coverage gaps, or after a batch of code edits in a project with a .chisel/ DB (or to bootstrap one with chisel analyze).
Use when you need to generate a complete test suite for a project — dispatches test-strategist, unit-test-writer, integration-test-writer, e2e-test-writer, and test-reviewer in sequence to produce strategy, implementation, and review artifacts. Covers test pyramid design, unit/integration/E2E implementation, coverage…
Analyze PR or local code changes and find Zebrunner test cases to run for regressions and new coverage gaps. Use when the user mentions test impact, PR test planning, which tests to run, regression coverage, sprint PR rollups, /test-impact, /test-impact-period, or Zebrunner + pull request / code changes.
Configure flowproof's SAP GUI, Fiori, and AI authoring credentials by walking the user through flowproof config sap / flowproof config fiori / flowproof config ai. Use when the user wants to set up, change, or check their SAP/Fiori login or model authoring key, or when a flow run fails because SAPUSER, FIORIPASSWORD…
QAs a PrestaShop pull request against an environment that is already running, in a real browser, on the command line or over HTTP, and writes an HTML report stating whether it is approved, with the recording as proof. Use when the user says "QA this PR", "test this pull request", "check that this fix works"…
Write, test, deploy and debug Ganju custom tools (Functions) with the ganju CLI and the @ganju/sdk handler API. Use this whenever the user works in a folder with a ganju.json, imports @ganju/sdk or defineTool, mentions @ganju/cli or any ganju command (init, link, build, test, deploy, logs, versions, rollback, secret…
Pin a shell guardrail (a hook, a git hook, a checker script) with a behavioral test suite, prove the suite is real by mutating the code, and wire it into CI with its mutation ledger. Use when asked to "add tests for this hook", "pin that guard", "mutation-test this script", "this hook has no test", "wire the suite…
Developing and deploying the starfleetctl source itself — claim protocol, make, bootstrap, daemon restarts in the right order, end-to-end verification. Load before editing anything in a starfleetctl source checkout, before running starfleet-bootstrap, or when a web/plugin change 'is done' but the fleet does not see it.
★not rated 5
changed 14d agoA72 tokens
AGPL-3.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: