GitHub
testing-anti-patterns
Use to avoid critical testing mistakes. Five Iron Laws: Never test mock behavior, Never add test-only methods, Never mock without understanding, Always integration test, Always test error paths.
Skills IA documentation testing
Découvrez les skills documentation testing, comparez leurs dépôts et consultez leurs instructions.
Catégories: documentation testing
documentation testing Effacer les filtres
Explorer
GitHub
tdd
Test-Driven Development workflow with RED-GREEN-REFACTOR cycle
GitHub
playwright-llm
Browser automation using Playwright for web navigation, content extraction, and interaction. Use when you need to browse websites, scrape content, or interact with web pages.
GitHub
analyze-test-coverage
Analyze test coverage gaps and report findings
GitHub
add-unit-tests
Write failing unit tests for feature requirements (TDD style)
GitHub
test-planning
This skill should be used when the user needs to create comprehensive test plans, define test cases and coverage strategies, validate test completeness, analyze ticket requirements for testing needs, or documen...
GitHub
test-planning
This skill should be used when the user asks to "create a test plan", "write test cases", "plan testing strategy", "define test coverage", "create test scenarios", or needs guidance on comprehensive test planni...
GitHub
qa-verify
AI-powered QA verification using Playwright MCP for visual E2E testing. Use when (1) Verifying UI changes after code modifications, (2) Testing user workflows end-to-end, (3) Checking for visual regressions, (4...
GitHub
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
GitHub
codereview-testing
Review test coverage and quality. Analyzes unit tests, integration tests, determinism, and test design. Use when reviewing test files or code that should have tests.
GitHub
codereview-api
Review API contracts, breaking changes, and interface consistency. Analyzes REST/RPC endpoints, event schemas, versioning, and backward compatibility. Use when reviewing public interfaces, API routes, or servic...
GitHub
chrome-devtools
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automa...
GitHub
test-standards
Testing best practices and anti-patterns. Use when writing tests, reviewing test quality, or understanding testing methodology for this project.
GitHub
qa-execution
Skill for executing tests, verifying results, and reporting bugs.
GitHub
qa-design
Skill for designing structured test flows and scenarios (Positive, Negative, Monkey, Security).
GitHub
skill-detection-test
Verifies that Claude Code can detect and load Skills. Use this to test skill discovery.
GitHub
testing-requirements
Use when writing tests - test structure, mocking patterns, pre-commit checks
GitHub
testing-expert-2026
Expert testing patterns for GhostSpeak monorepo (January 2026). Use when (1) Writing unit tests, (2) Building integration tests, (3) Creating E2E tests with Playwright, (4) Testing Solana programs, (5) Testing...
GitHub
test-gen
Generate comprehensive pytest integration tests for MCP tools and FastAPI endpoints. Includes fixtures, edge cases, and validation tests.
GitHub
tdd-workflow
Test-Driven Development process knowledge, quality standards, and workflow guidance
GitHub
ui-testing
Resilient React component testing strategies focusing on user behavior. Use when writing or reviewing UI tests, fixing flaky tests, or establishing testing patterns.
GitHub
testing-patterns
Unit testing patterns with Vitest. Use when writing tests for TypeScript code.
GitHub
testing-patterns
Test design patterns, best practices, and examples for comprehensive Solidity testing. Use when writing tests for smart contracts or improving test coverage.
GitHub
vitest-configuration
Vitest setup and best practices. Use when configuring Vitest for TypeScript projects.
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é.