GitHub
evidence-verification
Use when completing tasks, code reviews, or deployments to verify work with evidence. Collects test results, build outputs, coverage metrics, and exit codes to prove work is complete.
☆ 98Voir le skill
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
test-standards-enforcer
Enforce testing best practices - AAA pattern, naming conventions, isolation, coverage thresholds. Blocks non-compliant tests. Use when writing or reviewing tests.
☆ 98Voir le skill
GitHub
kata-verifying-work
Use this skill when validating built features through conversational testing, running UAT, user acceptance testing, checking if features work, or verifying implementation. Triggers include "verify work", "test...
☆ 97Voir le skill
GitHub
test-driven-development-tdd
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure fir...
☆ 96Voir le skill
GitHub
ios-testing-patterns
XCTest and XCUITest execution workflows and flaky test detection patterns
☆ 95Voir le skill
GitHub
writing-go-tests
Applies current Go testing best practices. Use when writing or modifying Go test files or advising on Go testing strategies.
☆ 95Voir le skill
GitHub
testing-anti-patterns
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behaviour, production pollution with test-only methods, and mocking without under...
☆ 95Voir le skill
GitHub
testing
Write, configure, and run unit + integration tests using project-independent best practices; detect tooling; triage failures/flakes; keep a compact Testing State Capsule.
☆ 95Voir le skill
GitHub
test-driven-development
Implement test-driven development (TDD) workflow using the red-green-refactor cycle. Use when writing new features, fixing bugs, or refactoring existing code. Always write the failing test first, then implement...
☆ 95Voir le skill
GitHub
playwright-automation
Automate browser testing, web scraping, and user workflow testing with Playwright across multiple browsers. Use when writing end-to-end tests for web applications, automating repetitive browser tasks, scraping...
☆ 95Voir le skill
GitHub
e2e-testing
Write comprehensive end-to-end tests that verify complete user workflows, integration between components, and system behavior from user perspective using Playwright, Cypress, or similar frameworks. Use when tes...
☆ 95Voir le skill
GitHub
lading-optimize-validate
Validates discovered bugs with reproducing tests and validates fixes with regression tests. Called by other skills when bugs are found during optimization hunting. Creates property tests (proptest) and Kani pro...
☆ 93Voir le skill
GitHub
testing
Write tests following TDD principles. Use when implementing features, fixing bugs, or adding test coverage. Covers e2e, integration, and unit testing patterns.
☆ 92Voir le skill
GitHub
strict-enforcement
Use when running claudikins-kernel:verify, checking implementation quality, deciding pass/fail verdicts, or enforcing cross-command gates — requires actual evidence of code working, not just passing tests
☆ 92Voir le skill
GitHub
testing-prpm-cli
Use when testing PRPM CLI commands locally - provides build, environment setup, execution workflow, contract testing to verify documented behavior matches implementation, and comprehensive cross-format conversi...
☆ 92Voir le skill
GitHub
fixing-flaky-tests
Diagnose and fix tests that pass in isolation but fail when run concurrently. Covers shared state isolation and resource conflicts. References condition-based-waiting for timing issues.
☆ 91Voir le skill
GitHub
elasticity-lab
Use to run pricing elasticity experiments with consistent assumptions and guardrails.
☆ 90Voir le skill
GitHub
quality-gates
Use when establishing tests, monitoring, and incident response for analytics models.
☆ 90Voir le skill
GitHub
playwright-debugging
Use when Playwright scripts fail, tests are flaky, selectors stop working, or timeouts occur - provides systematic debugging approach for browser automation issues
☆ 89Voir le skill
GitHub
writing-good-tests
Use when writing or reviewing tests - covers test philosophy, condition-based waiting, mocking strategy, and test isolation
☆ 89Voir le skill
GitHub
playwright-patterns
Use when writing Playwright automation code, building web scrapers, or creating E2E tests - provides best practices for selector strategies, waiting patterns, and robust automation that minimizes flakiness
☆ 89Voir le skill
GitHub
property-based-testing
Use when writing tests for serialization, validation, normalization, or pure functions - provides property catalog, pattern detection, and library reference for property-based testing
☆ 89Voir le skill
GitHub
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof aga...
☆ 89Voir le skill
GitHub
ln-510-test-planner
Orchestrates test planning pipeline (research → manual → auto tests). Coordinates ln-511, ln-512, ln-513. Invoked by ln-500-story-quality-gate.
☆ 89Voir le skill
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é.