unit-testing
Deprecated. Use testing/extension-testing (references/unit.md) for MetaMask Extension, or testing/mobile-testing (references/unit.md) for MetaMask Mobile. Kept…
Skills
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-01 00:15
Testing & quality
13,007 results
visual-testing
Drives the MetaMask Chrome extension via the mm CLI for visual testing in headedless Chrome. Use when asked to visually verify UI changes, capture screenshots or debug extension UI state. Trigger phrases include "verify visually", "take a screenshot", "test the flow", and "check the UI".
chromatic
Automates visual regression testing for Storybook components using cloud-based snapshot comparison. Use when setting up visual testing, catching UI…
code-quality
Audits code for security vulnerabilities, performance issues, accessibility, complexity metrics, and infrastructure security. Use when reviewing code quality,…
code-smell-detector
Detects code smells, anti-patterns, and common bugs with quantified thresholds and severity scoring. Use when reviewing code quality, finding maintainability…
mobile-parity-check
Compare the UI and UX of iOS and Android apps in either direction. Pin the reference versions, create isolated branches in both repositories, launch simulators…
difftool
Visual regression diffs between two URLs or two images with microlink difftool, via its CLI, its GitHub Action (sticky PR comment with screenshots), or the web…
writing-unit-tests-csharp
Guidelines and patterns for writing unit tests in C# using MSTest SDK.
retrospective
Review how work went and improve the next round. USE WHEN asked for a retro, delays, or process lessons. DO NOT USE for code review or transcript replay.
second-opinion
Independent review of current work or a past session. USE WHEN a user wants a second opinion. DO NOT USE WHEN ordinary code review is wanted — use code-review.
amplifier-digital-twin-universe
Stand up isolated, realistic environments from a declarative profile so software can be tested as though actually deployed. Use when (1) "the tests pass on my…
create-test-baseline
Create a test baseline for the project to be modernized. The baseline will be used for later verification of modernization tasks.
verify-test-baseline
Generate and run post-migration tests from the frozen baseline specification.
powertoys-module-verification
Verify a single PowerToys module's release checklist items end-to-end. Drive each checkbox via UIA / Named Events / settings.json edits / clipboard inspection…
rego-fuzzer
Pass the rego-cpp Trieste fuzzer for a given pass collection. Use when: verifying that compiler passes are robust to all valid WF inputs, debugging fuzzer…
code-review
Review pull requests for MSTest and Microsoft.Testing.Platform with TestFx-specific checks. Use for every GitHub Copilot code review in this repository, with…
dotnet-test-frameworks
Reference data for .NET test framework detection patterns, assertion APIs, skip annotations, setup/teardown methods, and common test smell indicators across…
generate-testability-wrappers
Generate wrapper interfaces and DI registration for hard-to-test static dependencies in C#. Produces IFileSystem, IEnvironmentProvider, IConsole,…
testfx-acceptance-validation
Validate TestFx shipping paths and capable CI execution using packed consumers, package/cache provenance, exact exits and artifacts, and…
run-e2e-tests
Run E2E tests to verify complete user workflows like environment discovery, creation, and selection. Use this before releases or after major changes.
run-smoke-tests
Run smoke tests to verify extension functionality in a real VS Code environment. Use this when checking if basic features work after changes.
use-component-explorer
Read this skill when the project uses the component explorer and you deal with UI (fixtures, screenshots, visual testing, read when adding/changing UI).
debug-fixed
User confirms the bug is fixed. Clean up instrumentation and summarize.
debug-fixed
User confirms the bug is fixed. Clean up instrumentation and summarize.