testing
lobehub/lobehub/.agents/skills/testing/SKILL.md
Use for Vitest tests, mocks, coverage and failing-test diagnosis.
Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
lobehub/lobehub/.agents/skills/testing/SKILL.md
Use for Vitest tests, mocks, coverage and failing-test diagnosis.
iOfficeAI/AionUi/.claude/skills/testing/SKILL.md
Testing workflow and quality standards for writing and running tests. Use when: (1) Writing new tests, (2) Adding a new feature that needs tests, (3) Modifying logic that has existing tests, (4) Before claiming a task is complete.
JetBrains/intellij-community/.agents/skills/testing/SKILL.md
Run or troubleshoot IntelliJ `tests.cmd` tests and discovery.
JetBrains/intellij-community/.claude/skills/testing/SKILL.md
Run or troubleshoot IntelliJ `tests.cmd` tests and discovery.
kortix-ai/suna/.agents/skills/testing/SKILL.md
Use for every Kortix test task, behavior change, bug fix, refactor, API route change, CLI change, SDK change, browser journey, test failure, coverage question, local benchmark, or testing infrastructure change. Enforce the single local-first runner, black-box flow contracts, package-local SDK tests, browser-only Playwright tests, and real input/output verification.
modelcontextprotocol/inspector/.claude/skills/testing/SKILL.md
Run, place and fix tests in this repo. Use when choosing which npm command runs a given suite (web unit, web integration, Storybook, cli, tui, launcher, scripts); when deciding where a new test file belongs — beside its source, under src/test/, or in a client's __tests__/; when a per-file coverage check fails or a v8 ignore is in question; when asking which test tier spawns the built binary rather than importing it; or when rendering, mounting or asserting on Mantine components and their transitions in a test.
microsoft/fast/.github/skills/testing/SKILL.md
Use this skill when running or writing tests in the FAST monorepo — local test execution, CI workflows, Playwright fixtures, and WebUI integration testing.
bytebase/dbhub/.claude/skills/testing/SKILL.md
Run and troubleshoot tests for DBHub, including unit tests, integration tests with Testcontainers, and database-specific tests. Use when asked to run tests, fix test failures, debug integration tests, troubleshoot Docker/database container issues, or add new tests. Also use when verifying code changes work correctly or when CI test failures need investigation.
BankrBot/skills/ethskills-testing/SKILL.md
Smart contract testing with Foundry — unit tests, fuzz testing, fork testing against live state, and invariant testing. What to test, what to skip, and what LLMs commonly get wrong.
vm0-ai/vm0/.claude/skills/testing/SKILL.md
Comprehensive testing patterns and anti-patterns for writing and reviewing tests
cloudflare/sandbox-sdk/.agents/skills/testing/SKILL.md
Use when writing or running tests for this project. Covers unit vs E2E test decisions, test file locations, mock patterns, and project-specific testing conventions. (project)
affaan-m/ECC/.agents/skills/e2e-testing/SKILL.md
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies. Use when writing Playwright tests, structuring page objects, or fixing flaky E2E runs in CI.
microsoft/aspire/.agents/skills/pr-testing/SKILL.md
Use when asked to test a microsoft/aspire pull request, including CLI, hosting, dashboard, component, template, and VS Code extension changes. Also covers testing PRs that change CI infrastructure — GitHub Actions (workflows, actions, gh-aw agentic workflows, CI scripts under .github/ and eng/) and Azure DevOps pipelines (eng/pipelines, eng/common).
anthropics/knowledge-work-plugins/finance/skills/sox-testing/SKILL.md
Generate SOX sample selections, testing workpapers, and control assessments. Use when planning quarterly or annual SOX 404 testing, pulling a sample for a control (revenue, P2P, ITGC, close), building a testing workpaper template, or evaluating and classifying a control deficiency.
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.
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.
xu-xiang/everything-claude-code-zh/.agents/skills/e2e-testing/SKILL.md
Playwright E2E 测试模式、页面对象模型(POM)、配置、CI/CD 集成、产物管理以及不稳定测试(flaky test)策略。
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.