GitHub
comprehensive-testing
Guidelines for thorough testing
Explorer
Explorez des skills pour le développement, le contenu, les données et la productivité. Comparez les descriptions et dépôts.
Catégories
Explorer
GitHub
testing-code
Writes comprehensive tests following AAA pattern. Use for unit and integration tests.
GitHub
spec-drafting
Replaces the actual work of drafting and updating detailed specifications that can be used directly as input for TDD using templates based on plans. Typical use cases: (1) Formulating rigorous API contracts def...
GitHub
vitest-testing-expert
Vitest testing framework expert for Vite integration, Jest migration, browser mode testing, and performance optimization
GitHub
verifyepic
Verify epic completion by checking child features and running verify target
GitHub
pf-test-hook
커스텀 훅 테스트 생성. "훅 테스트", "hook 테스트" 요청 시 사용.
GitHub
17th-test-analyzer
Use this skill when user asks about test coverage, test sufficiency, or whether tests cover requirements. Analyzes staged changes against task spec using GPT-5.2-Codex to find gaps in happy cases and edge cases...
GitHub
go-test-generator
Generates table-driven tests for Go functions
GitHub
auto-test-generator
AI generates comprehensive Jest tests automatically for COE TypeScript code, similar to q4test but for general-purpose testing
GitHub
python-test-strategy
Enforces Dave Farley–style fast feedback by defining Python unit, adapter, contract, and acceptance testing playbooks; use when planning or diagnosing tests.
GitHub
unit-testing-test-generate
You are a test automation expert specializing in generating comprehensive, maintainable unit tests across multiple languages and frameworks. Create tests that maximize coverage, catch edge cases, and
GitHub
test-guidelines
Comprehensive testing guidelines for Vitest and React Testing Library. Covers quality standards, AAA pattern, naming conventions, branch coverage, and best practices. Reference this skill when creating or updat...
GitHub
gen-property-test
Generate fast-check property tests following project conventions
GitHub
test
Run tests for the Pitfal Solutions project. Supports unit tests, E2E tests, and coverage reporting.
GitHub
fluent-assertions
Creates readable test assertions with FluentAssertions library. Use when: writing unit tests, integration tests, verifying object state, testing exceptions, asserting collections
GitHub
storybook-guidelines
Comprehensive Storybook story creation guidelines. Covers story structure, naming conventions, and visual testing patterns. Reference this skill when creating Storybook stories for components with conditional r...
GitHub
run-backend-tests
Run Python tests for the AIQ backend. Handles venv activation and pytest execution. Use this whenever you need to run backend tests.
GitHub
mocking-patterns
Jest mocking patterns, jest.fn(), jest.mock(), spies, module mocking, dependency injection, mock implementations. Activates when user mentions "mock", "jest.fn", "jest.mock", "spy", "stub", "fake", "dependency...
GitHub
tdd-python-drafting
Replaces the creation of test code based on specifications and the minimal implementation to pass them (Red/Green) in Python projects. Typical use cases: (1) Creating failing tests (Red) based on API or logic s...
GitHub
testing-and-quality-assurance
Testing patterns for Python Flask APIs, ML translation models, and database operations. Use when writing tests, setting up test fixtures, or validating translation accuracy for the Chuuk Dictionary application.
GitHub
alpha-production-readiness-trace
Production readiness evaluation for alpha that traces UI flows end-to-end (UI -> API -> backend -> persistence/integrations), defines what each flow should and should not do, finds stubbed or missing behavior,...
GitHub
qa-level-assessment
QAテストレベルを判定するスキル。ストーリー説明文、コード差分、対話形式を組み合わせて総合的にリスクを評価し、適切なQAレベルを提案する。 以下の場面で使用: - PRのQAレベルを判定したい時 - テスト実施者・ダブルチェッ...
GitHub
verify
Run tests and fix issues end-to-end with Claude CodePro
GitHub
tdd-workflows-tdd-refactor
Use when working with tdd workflows tdd refactor
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é.