testing
ryu111/claude-workflow-config/skills/testing/SKILL.md
測試專業知識。測試金字塔、測試策略、邊界測試、Mock 最佳實踐。適用於撰寫和執行測試。
Often used withbundle-dependency-prsupdate-library-template
Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
ryu111/claude-workflow-config/skills/testing/SKILL.md
測試專業知識。測試金字塔、測試策略、邊界測試、Mock 最佳實踐。適用於撰寫和執行測試。
Often used withbundle-dependency-prsupdate-library-template
Scoop-technology/claude-code-skills/skills/testing/SKILL.md
Testing strategy, coverage analysis, and quality assurance. Use when: (1) Planning test strategy for a story, (2) Analyzing test coverage, (3) Reviewing test quality in PRs, (4) Creating mocks for integrations, (5) Defining testing standards. Referenced by developer-analysis (test strategy in design) and git-workflow (PR review test verification).
Often used withbundle-dependency-prsupdate-library-template
swapnil-saal/agentic-react-starter/.claude/skills/testing/SKILL.md
How to test in this repo — the verification loop, the four unit-test archetypes, MSW mock handlers, and Playwright e2e. Use when writing or fixing any test, adding a mock endpoint, or deciding whether a change is adequately covered.
Often used withbundle-dependency-prsupdate-library-template
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
Often used withbundle-dependency-prsupdate-library-template
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
Often used withbundle-dependency-prsupdate-library-template
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.
Often used withbundle-dependency-prsupdate-library-template
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.
Often used withbundle-dependency-prsupdate-library-template
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.
Often used withbundle-dependency-prsupdate-library-template
TJM-NZ/claude-skills/testing/SKILL.md
Test strategy, audit and writing - decides what is worth testing and at which level, audits an existing suite for tests that can't fail, flakiness and gaps in risky behaviour, or writes missing unit, integration and E2E tests that follow the project's conventions. Stack-agnostic.
Often used withbundle-dependency-prsupdate-library-template
zeeshanalimughal/claude-skills/skills/testing/SKILL.md
Test strategy and patterns — what to test, how to structure tests, mocking rules, and flaky-test prevention. Use when writing tests, setting up a test suite, or deciding how to verify code works.
Often used withbundle-dependency-prsupdate-library-template
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.
No other project uses it yet
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.
No other project uses it yet
abpframework/abp/.agents/skills/abp-testing/SKILL.md
ABP testing patterns - integration tests over unit tests, GetRequiredService, IDataSeedContributor, Shouldly assertions, AddAlwaysAllowAuthorization, NSubstitute mocking, WithUnitOfWorkAsync. Use when writing or reviewing tests for application services, domain services, or repositories in ABP projects.
No other project uses it yet
apereo/cas/.claude/skills/cas-testing/SKILL.md
Run and write tests in the CAS Gradle monorepo: testcas.sh categories, JUnit tags, single-module test tasks, fast compile checks, how tests stay correct under JUnit parallel execution (shared registries, ports, pac4j clients, negative assertions), test authentications and principal attributes, and ticket-granting cookies in MockMvc tests. Use when running tests, choosing a test category, writing or fixing a *Tests.java class, or chasing a flaky test.
podman-desktop/podman-desktop/.agents/skills/mcp-testing/SKILL.md
Interactive testing of Podman Desktop UI using the electron-test MCP server. Supports both production (installed app) and development (pnpm watch) modes. Use for manually testing UI workflows, debugging UI issues, exploring features, or quick acceptance testing.
2 projects use a version of this
alphaXiv/OpenResearch/.agents/skills/orx-testing/SKILL.md
Test an OpenResearch change the way its user will find the problems, and bring evidence a reviewer can see. Covers starting from the right state, driving the real flow from its entry point, real agents and backends, states, themes, sizes, languages and failure cases, the desktop webviews on macOS, Windows and Linux, screenshots and video and checking each frame. Use before calling any change a user can see done, before filing or updating a pull request, when asked to test, verify, screenshot, record or QA, and whenever a user reports a bug that "the tests pass" on. In this repo, use it in place of any general UI testing skill, including when reviewing someone else's change.
Steady7 mentions in 2 weeks
No other project uses it yet
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".
alex-ilgayev/MCPSpy/.claude/skills/go-testing/SKILL.md
Handles all Golang testing tasks including running tests, writing new tests, and fixing test failures. Follows MCPSpy testing conventions with require for critical assertions and assert for non-critical ones.
nginx/kubernetes-ingress/.github/skills/nic-testing/SKILL.md
Testing patterns for NIC including Go table-driven tests, snapshot tests, and Python integration tests. Use when writing unit tests, snapshot tests, policy tests, template tests, Helm tests, or pytest integration tests for the Ingress Controller.
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.