systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Découvrez les skills testing security testing, comparez leurs dépôts et consultez leurs instructions.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Verifies environment setup, configs, and system requirements
Use when implementing an APPROVED OpenSpec change. Read tasks.md and follow EXACTLY. Do not deviate, add features, or skip tasks. Use with test-tdd for each code task.
Test game via browser with Chrome DevTools. Navigate UI, play through game flow, observe behavior and report issues.
Run tests before and after changes. Only add tests for complex logic, not boilerplate. Database tests matter most.
Use BEFORE any implementation to check if specs exist for the capability. Run this first when starting any feature work. Reports: spec exists, no spec, or active change in progress.
Launch Leavn app in iOS simulator, navigate features using MCP browser tools, take screenshots, verify UI rendering and feature functionality
You are the quality assurance architect ensuring Leavn's critical paths are protected by tests.
Run, debug, and structure tests for this Go project (unit + integration), including generation prerequisites. Use when changing domain logic, repositories, HTTP handlers, or migrations.
Run and extend the end-to-end HTTP integration tests (SQLite in-memory) for mjr.wtf, covering auth, create/list/delete, redirects, and analytics. Use when changing handlers, middleware, or API contracts.
Limpa conversas de teste do CarInsight
Executa testes unitários, integração e E2E do CarInsight
(opencode-project - Skill) Implement comprehensive testing for Cloudflare Workers and SvelteKit applications using Vitest, Playwright, and Miniflare for unit, integration, and end-to-end testing in serverless e...
Maintain BDD-style Playwright E2E tests and a human-readable scenario catalog for the Progress Tracker repo. Use when adding/updating scenarios in e2e/SCENARIOS.md, implementing them in e2e/bdd.spec.ts, or fixi...
Generate small animated GIFs for each Playwright BDD scenario and surface them in-app as usage instructions.
Python testing best practices with pytest. Covers unit, integration, async tests, mocking, fixtures. Triggers: "write tests", "add tests", "test coverage", "pytest", "unit test", "integration test"
Browser automation using Vercel's agent-browser CLI. Use when you need to interact with web pages, fill forms, take screenshots, or scrape data. Alternative to Playwright MCP - uses Bash commands with ref-based...
Vitest, Playwright, and testing strategies. Use when writing tests, setting up test infrastructure, or debugging test failures.
Use when about to claim work is complete, fixed, or passing. Invoke BEFORE committing, creating PRs, or making any success claims. The Iron Law - evidence before assertions, always.
Use when implementing any feature, bugfix, or code change. Invoke BEFORE writing implementation code. The Iron Law - no production code without a failing test first.
Creating Storybook documentation with proper stories, argTypes, model instances, and variations
An agent that codes tasks in BDD-style. Automatically does not commit.
実装のテスト、リファクタリング、ポータビリティ、ディレクトリ階層について議論する際に、絶対パスが実装コードに存在しないことを確認する
Validate implementation against test cases and acceptance criteria. Use when checking if code works correctly, validating against user-provided test cases, or verifying acceptance criteria are met. Gets test ca...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.