testing-compatibility
Test application compatibility across browsers, devices, and platforms
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 10-23 00:13
12,554 results
Test application compatibility across browsers, devices, and platforms
Mock Service Worker (MSW) 2.x for API mocking. Use when testing frontend components with network mocking, simulating API errors, or creating deterministic API…
Cross-language testing strategies and patterns. Triggers on: test pyramid, unit test, integration test, e2e test, TDD, BDD, test coverage, mocking strategy,…
Guide for testing code changes in AEM Edge Delivery projects including blocks, scripts, and styles. Use this skill after making code changes and before opening…
The business diagnostic assistant is suitable for operations, managers, manufacturing, and 8D when users ask questions such as "how should this be done," need to quickly break down goals, determine priorities, and form executable results, helping generate summaries, diagnostic conclusions, action recommendations, and reusable deliverables based on input materials.
Work out what to change in a project's test environment so Agent swarm stops getting blocked when it tests against a live backend — seed better test data,…
Route and coordinate one or more Appium driver setup requests by handing UiAutomator2, Espresso, Chromium, Gecko, Mac2, Safari, or XCUITest to its dedicated…
Validates that a skill's companion scripts declare their OS and binary dependencies correctly, and checks whether those dependencies are actually present on…
Quality review skill for verifying complex changes against criteria. Use for multi-file changes, new features, or before important commits. Skip for trivial…
Structured code review across correctness, security, performance, readability, testing, and architecture, with language-specific guidance and human-readable…
Testing strategies and ansible-lint configuration for validating Ansible automation quality, covering lint rules, syntax validation, and integration test setup.
Use only for reviewing completed Biome PRs, branches, commit ranges, diffs, or working trees against business logic and requirements. Excludes broad…
Analyzes a bug-fix commit or PR and produces a structured Root Cause Analysis report covering what went wrong, why, and what guardrails failed.
Use when the user mentions accessibility checking, App Store submission, code review, or WCAG compliance.
Use when the user mentions GRDB performance review, slow GRDB queries, app-group database setup audit, a ValueObservation that stopped updating, or pre-release…
Use when the user wants a comprehensive project-wide audit, full health check, or scan across all domains.
WHEN deciding whether a PR, branch, diff, or current implementation satisfies an authoritative issue, specification, or decision contract; NOT for improving the written artifact, reconstructing meetings, general code review, or implementing fixes. Returns a read-only criterion-by-criterion proof and acceptance verdict.
Upgrade Obsidian wikis to latest format. Handles structure migration (phases/tasks → features/specs), comment format upgrades (adding emoji prefixes), and…
Use when implementing any feature or bugfix, before writing implementation code
Use when code has been written and needs validation before committing, or when the user asks for a code review or security check.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
[Testing] Use when you need to generate or review integration tests.
Unified quality gate skill for pre-delivery checklist, security checks, testing strategy, and handover readiness.
Full-Stack Engineer request handler workflow. Use when receiving any user request to properly classify tasks (CONSULT/BUILD/DEBUG/OPTIMIZE) and execute the…