webstatus-e2e
Use when writing, modifying, or debugging Playwright end-to-end (E2E) tests for webstatus.dev.
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Use when writing, modifying, or debugging Playwright end-to-end (E2E) tests for webstatus.dev.
Verify numerical claims in documentation are still accurate
Gate quantitative Mira conclusions by requiring reproducible data, formulas, calculation ledgers, or explicit downgrades when numbers drive judgment.
Audible code-quality reactions for code reading, review, refactoring, debugging, and repository exploration. Use when the user wants Codex to scan code and play escalating groaning sounds based on suspicious code quality signals, especially requests like "make Codex suffer while reading this code", "play sounds based on code quality", "audible code review", or explicit use of $endless-toil.
Use when Playwright scripts fail, tests are flaky, selectors stop working, or timeouts occur - provides systematic debugging approach for browser automation issues
Post-deploy verification: execute AVP from tech-spec on live environment, verify all acceptance criteria (user-spec + tech-spec), pick up deferred criteria from pre-deploy QA report. Uses MCP tools (Telegram MCP, Playwright, curl, bash). Use when: "пост-деплой проверка", "post-deploy verification", "проверь после деплоя", "MCP verification", "верификация на живом окружении", "проверь деплой", "запусти AVP", "agent verification plan"
Pre-deploy acceptance testing methodology: run test suite (unit/integration/E2E), verify acceptance criteria from user-spec and tech-spec. Does not require live environment. Use when: "приёмочное тестирование", "pre-deploy qa", "проверь перед деплоем", "run tests and check AC", "запусти qa", "проверь acceptance criteria", "тестирование фичи", "qa", "проверь фичу"
Testing methodology: when to write which tests, how to ensure test quality, test pyramid strategy. Use when: "напиши тесты", "как тестировать", "проанализируй тесты", "проверь качество тестов", "ревью тестов", "тестовая стратегия"
Perform a read-only ISIS3 PR-readiness review, especially for legacy Makefile-to-gtest/CTest conversions. Check build-system integration, fixtures and data, scientific assertions, reviewer-comment resolution, and git hygiene.