Claude skills and agent skills

pastropsucezSkill

testing

pastropsucez/vibe-stack/.claude/skills/testing/SKILL.md

Run tests, check builds, and validate the application works correctly. Use after making changes.

Often used withbundle-dependency-prs·update-library-template

rohanmistry231Skill

testing

rohanmistry231/Claude-Code-Project-Structure-Learning-Repository/.claude/skills/testing/SKILL.md

Skill: Testing ## Description Write, run, or fix tests for the Blog API using pytest and httpx. ## When to Use Trigger this skill when the user says: - "write tests", "add tests

Often used withbundle-dependency-prs·update-library-template

theishandubeySkill

testing

theishandubey/dotclaude/skills/testing/SKILL.md

How implementers and fixer test their changes - unit tests for every change, end-to-end tests only when the user asks, the shape of each, setting up a harness, how to run them and output discipline. Preloaded by implementer, parallel-implementer and fixer.

Often used withbundle-dependency-prs·update-library-template

TiagoJacintoSkill

testing

TiagoJacinto/skills/testing/SKILL.md

Testing taxonomy: test purposes, levels, verification modes, and doubles. Use when choosing the kind of test, its boundary, or how to observe its subject.

Often used withbundle-dependency-prs·update-library-template

timmo001Skill

testing

timmo001/notes/.agents/skills/testing/SKILL.md

Choose tests for their concrete regression value, avoid low-value coverage, and verify changes by exercising the real built behaviour. Use during implementation, fixes, planning, diagnosis, and code review when choosing verification, adding or changing tests, considering a missing-test finding, or when the user asks to test, check, or verify a change.

Often used withbundle-dependency-prs·update-library-template

yacb2Skill

testing

yacb2/aidex/skills/testing/SKILL.md

Use when about to write, add or change a test in any project — a unit, component, API or E2E test, a regression test for a bug, or tests for a change just made. Preloaded into code-writing agents (implementation and bugfix) so the authoring core is in context before the first test file is written. Fires on "write a test for", "add a regression test", "add tests for this change", "cover this with a test", "write a Playwright spec for". Not for: planning or auditing a suite, choosing which tests to run, fixtures, the E2E environment or the testing profile (/aidex:coverage); the RED-first bug-fix procedure (/aidex:bugfix).

Often used withbundle-dependency-prs·update-library-template

OpenHandsSkill

e2e-testing

OpenHands/OpenHands/.agents/skills/e2e-testing/SKILL.md

This skill should be used when the user asks to "add an E2E test", "run live E2E", "run mock-LLM tests", "debug Playwright CI", "test the Docker image", or changes tests/e2e, Playwright configs, E2E workflows, artifacts, or test reporting.

Often used witheverything-claude-code·everything-claude-code-conventions·bun-runtime

MicrosoftPipes a download into a shellSkill

pr-testing

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).

adelrodriguezSkill

testing

adelrodriguez/skills/skills/testing/SKILL.md

Use when writing, changing, or reviewing tests, or when fixing a bug.

Often used withbundle-dependency-prs·update-library-template

AndersonAndradSkill

testing

AndersonAndrad/skills/testing/SKILL.md

Defines mandatory testing practices for features, bug fixes, refactors, endpoints, business rules, integrations, and behavior changes. Use during implementation and before declaring any code task complete.

Often used withbundle-dependency-prs·update-library-template

andr-caSkill

testing

andr-ca/agentharness/.claude/skills/testing/SKILL.md

Use when writing tests, deciding on test coverage, choosing between unit/integration/E2E tests, applying TDD, or reviewing test quality — covers rigor tiers, the Red-Green-Refactor cycle, coverage requirements, and Playwright for UI testing.

Often used withbundle-dependency-prs·update-library-template

AntheaLaffySkill

testing

AntheaLaffy/the-missing-semester-skills/testing/SKILL.md

测试与覆盖率：单元/集成/功能测试、TDD、回归测试、性质测试（Hypothesis/QuickCheck）、 mock 外部依赖、行覆盖率与 Codecov。Use when the user asks to write tests, raise coverage, or choose a testing approach. 触发于「写测试/提覆盖率/选测试策略」。

Often used withbundle-dependency-prs·update-library-template

Autocss-comSkill

testing

Autocss-com/ai/.agents/skills/testing/SKILL.md

How to verify AutoCSS work before it ships, in a zero-dependency architecture. Covers the air-gap test, driving the real app in a browser to observe behavior, verifying CSS-only state/visibility, and the accessibility passes. Test tooling is dev-only and never enters the shipped static shell. Use before committing any nontrivial change, or when asked to confirm something works.

Often used withbundle-dependency-prs·update-library-template

BappozSkill

testing

Bappoz/My-Claude-Skills/skills/engineering/testing/SKILL.md

Estratégia e escrita de testes production-grade: pirâmide vs troféu, unit/integration/e2e, o que testar (comportamento, não implementação), test doubles, contract e mutation testing, cobertura útil. Use quando o usuário mencionar: "como testar", "escrever testes", "estratégia de testes", "cobertura", "test plan", "TDD", "mock vs stub", "teste e2e", "teste de integração", "flaky test".

Often used withbundle-dependency-prs·update-library-template

BrendenKennedyReads credentialsSkill

testing

BrendenKennedy/claude-for-ai-platforms/.claude/skills/testing/SKILL.md

How verification works in THIS repo — the cheapest-to-costliest confidence ladder and the exact commands that work today. Carries: the real test runner + invocation, the offline-safe rule (unit tests need no env/service/network/GPU — stub the boundary), the ML confidence checks (tiny-data smoke: a forward pass + one train step on a 2-sample fixture; determinism; split-leakage; metric sanity), the live/GPU-smoke pattern (skips cleanly when its dependency is down, self-cleans), readiness checks, and environment preconditions. Load BEFORE running or writing a test, verifying a change, or claiming something works. Triggers: run tests, verify, does this work, test this change, pytest, uv run pytest, smoke test, offline test, readiness check, integration test, CI, forward-pass smoke, shape mismatch, determinism test, leakage test, overfit one batch, does the model train, cuda available.

Often used withbundle-dependency-prs·update-library-template

byalex33Skill

testing

byalex33/skills/skills/testing/SKILL.md

While testing an implemented feature or fix, investigate incidental suspected bugs and file new, unrelated findings in the project's designated GitHub repository. Use during implementation testing, not as a request for a broader bug audit.

Often used withbundle-dependency-prs·update-library-template

caglarbaranboraSkill

testing

caglarbaranbora/Apple-Agent-Kit/skills/testing/SKILL.md

Route Apple-platform testing tasks to the correct Knowledge Contracts -- XCTestCase subclassing with test-prefixed methods and the per-test setUp()/setUpWithError()/tearDown()/tearDownWithError() lifecycle plus the XCTAssert family and XCTSkip/XCTSkipIf/XCTSkipUnless; the Swift Testing framework's @Test/#expect/#require/@Suite/Tag vocabulary; @Test(arguments:) parameterization (single-collection, two-collection Cartesian product, zip-paired) and async throws test functions in both frameworks; XCUIApplication/XCUIElement UI testing with identifier-based lookup; and XCTestExpectation for callback-based async code with no async/await entry point. Use when writing class Foo: XCTestCase, func test..., override func setUp()/setUpWithError()/tearDown()/tearDownWithError(), XCTAssertEqual/XCTAssertTrue/XCTAssertNil/XCTAssertThrowsError, XCTSkip/XCTSkipIf/XCTSkipUnless, import Testing, @Test, @Suite, #expect(_:), #require(_:), .tags(_:), @Test(arguments:), zip(...) inside @Test(arguments:), async throws test methods, XCUIApplication(), .launch(), continueAfterFailure, app.buttons["..."], .tap(), .typeText(_:), .waitForExistence(timeout:), XCTestExpectation, expectation(description:), .fulfill(), or await fulfillment(of:timeout:). v1 covers only XCTest, Swift Testing, and XCUITest as described -- no performance testing (measure { }, XCTMetric, XCTClockMetric), no Xcode Test Plans or code coverage configuration, no third-party snapshot testing, no UI test recording, no mocking/dependency-injection/test-double patterns, and no performAccessibilityAudit(). Triggers on XCTest, XCTestCase, XCTAssert, XCTSkip, Swift Testing, @Test, #expect, #require, @Suite, Tag, parameterized test, XCUITest, XCUIApplication, XCUIElement, accessibilityIdentifier, XCTestExpectation, fulfillment.

Often used withbundle-dependency-prs·update-library-template

conjurer-richSkill

testing

conjurer-rich/skills/skills/engineering/testing/SKILL.md

Testing patterns for behavior-driven tests. Use when writing tests, creating test factories, structuring test files, or deciding what to test. Do NOT use for UI-specific testing (see front-end-testing or react-testing skills).

Often used withbundle-dependency-prs·update-library-template

dboskSkill

testing

dbosk/claude-skills/testing/SKILL.md

IMPORTANT: load BEFORE planning, writing or changing code in a repository that has tests - features, bug fixes and refactors too, not only requests that mention tests - and before writing a plan's Tests or Verification section. Makes a green run mean the real thing works: real code before fakes, recorded live data before hand-written mocks or fake responses, live drift checks, red/green, mutation checks, and no personal data in test data or output. Also use when (1) writing, fixing, reviewing or deleting tests, coverage or TDD; (2) mock, patch, monkeypatch, fake sessions or responses, VCR, cassettes or snapshots come up; (3) code calls an external service or API (Canvas, LADOK, SharePoint, GitHub, an LLM, a database), or you probe one by hand to check a change; (4) tests are flaky, pass while the code is broken, or break on every refactor; (5) test data or output may hold names, emails, personnummer or tokens. Pytest-centred; covers literate (.nw) projects.

Often used withbundle-dependency-prs·update-library-template

Dhi13manSkill

testing

Dhi13man/skivolve/skills/testing/SKILL.md

Reference test-design guidance used to exercise Skivolve without depending on a named external skill.

Often used withbundle-dependency-prs·update-library-template