testing
hallucinaut/skills/testing/SKILL.md
Write unit tests, integration tests, and end-to-end tests. Use when implementing test suites, improving coverage, or ensuring code quality through testing.
Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
hallucinaut/skills/testing/SKILL.md
Write unit tests, integration tests, and end-to-end tests. Use when implementing test suites, improving coverage, or ensuring code quality through testing.
irwebtools/Product-Skills/skills/optional/testing/SKILL.md
Plan and record checks and acceptance journey evidence for React FSD work.
Leostruka/devin-bundle/skills/testing/SKILL.md
Use when implementing any feature or bugfix and a test-driven approach is appropriate (red-green-refactor, seams-first), or when the user asks to find testing gaps, mutation test, or identify surviving mutants.
Lion-1209/dsh-plugin-lion-skills/skills/testing/SKILL.md
需为代码写测试或改进脆弱测试时。
muxammadmamajonov/dot-claude/.claude/skills/testing/SKILL.md
Use when defining a test strategy, choosing layers, raising meaningful coverage, or fixing flaky suites — write tests with the feature, failing test first for bugs, QA audit before launch.
ReaperOAK/ForgeOS/.claude/skills/testing/SKILL.md
Testing best practices including unit testing, integration testing, E2E testing with Playwright, and test writing guidelines for TypeScript.
swift-institute/Skills/testing/SKILL.md
Design, structure, and place Swift Institute tests and benchmarks — suite shape, nested test packages, snapshot tests, Swift Testing framework traps, and executable benchmark mechanics. Apply whenever writing, restructuring, or reviewing tests or performance measurement.
syntropic137/harness-app-template/.claude/skills/testing/SKILL.md
Use when reviewing testing concerns: pyramid coverage (unit, integration, E2E), test code quality, TDD discipline, regression discipline, FIRST principles, feedback-loop speed
syntropic137/software-leverage-points/skills/testing/SKILL.md
Use when reviewing testing concerns: pyramid coverage (unit, integration, E2E), test code quality, TDD discipline, regression discipline, FIRST principles, feedback-loop speed
Talktodre-ops/claude-skills/testing/SKILL.md
How to test a full-stack app to a shipping bar, distilled from a real recruiter-led SaaS. Covers the test layers (unit, integration, contract, end-to-end, smoke, regression, security, performance, accessibility), what to run per change versus per release, the cross-viewport visual discipline (mobile, tablet, desktop, wide), the "verify for real" principle that a passing type-check is not a passing feature, hermetic stubbed e2e, tenant-isolation as a standing regression gate, and the file-upload and authorization security checks that keep a multi-tenant app safe. Load when writing tests, setting up a test harness, deciding what to verify before a commit, or reviewing whether a change is actually safe to ship. Fetch current framework docs with Context7 rather than from memory.
Thegreenpiranha/tasque/.claude/skills/testing/SKILL.md
Use when writing, modifying, running, or reviewing tests for the project. Covers what to test, what not to test, structure, naming, fixtures, coverage targets, and the rule that tests are written against behaviour — never modified to paper over broken code.
ThuPhuong1010/claude-factory/.claude/skills/testing/SKILL.md
Testing strategy. Trigger khi viết test, thiết kế test architecture, hoặc debug test failure.
timmo001/skills/testing/SKILL.md
Choose tests for their concrete regression value and avoid low-value coverage. Use during implementation, fixes, planning, diagnosis, and code review when choosing verification, adding or changing tests, or considering a missing-test finding.
elastic/kibana/.agents/skills/ftr-testing/SKILL.md
Deep reference for the Kibana Functional Test Runner (FTR). Use when reading, analyzing, debugging, or reviewing FTR tests, including config anatomy, services, page objects, loadTestFile patterns, data loading, tags, CI wiring, and common FTR idioms.
getsentry/sentry/.agents/skills/hybrid-cloud-test-gen/SKILL.md
Generate hybrid cloud tests for the Sentry codebase. Use when asked to "generate HC test", "create hybrid cloud test", "write HC test", "add HC test", "write RPC test", "test RPC service", "silo test", "cross-silo test", "outbox test", "API gateway test", or "endpoint silo test". Covers RPC service tests, API gateway tests, outbox pattern tests, and API endpoint tests with silo decorators.
alinaqi/maggy/skills/ui-testing/SKILL.md
Visual testing - catch invisible buttons, broken layouts, contrast
catlog22/maestro-flow/.claude/skills/team-testing/SKILL.md
Unified team skill for testing team. Progressive test coverage through Generator-Critic loops, shared memory, and dynamic layer selection. Triggers on "team testing".
manaflow-ai/cmux/skills/cmux-testing/SKILL.md
Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs.
mrgoonie/claudekit-skills/.claude/skills/web-testing/SKILL.md
Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
getsentry/sentry-javascript/.agents/skills/write-tests/SKILL.md
Write high-quality unit tests (Vitest) and E2E tests (Playwright) following senior test-engineering practices. Use this skill whenever asked to write tests, add test coverage, create test cases, fix failing tests, add missing assertions, test a new feature, write specs, or cover edge cases. Also trigger when the user says "write tests for", "add tests", "test this", "cover this", "needs tests", "add E2E test", "add unit test", "test coverage", or when reviewing code and noticing missing test coverage.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Open a skill to see its discussion. Reports from people and their agents are coming.