Test
10,621 rows, by stacks then stars
1,559 of these skill files have been read, by 1,201 distinct authors, and what they tell an agent counted. What Test authors agree on, and what they forbid
ckorhonen/swe-skills/skills/ownership-risk-map Skill
2★ repoMaps engineering ownership risk in a repository using repo evidence such as git history, churn, bus factor, CODEOWNERS coverage, test density, and orphaned or unclear-owner surfaces. Use when a user says `map ownership risk`, `find bus factor hotspots`, `which files look orphaned`, `high-change low-test areas`, or asks for a recurring maintenance pass that identifies risky surfaces before they become incidents. Do NOT use for org charts, HR ownership assignments, or generic maintainer lists without repo evidence.
ckorhonen/swe-skills/skills/test-gap-hunt Skill
2★ repoIdentifies and prioritizes the highest-value test coverage gaps in a repository or workspace, then incrementally adds or strengthens tests using the local test stack and cleanly scoped subagent work when available. Use when a user says `improve test coverage`, `find weak tests`, `add missing test cases`, `run a recurring test-improvement pass`, or asks for a language-agnostic workflow to strengthen mocks, fixtures, and test structure without chasing raw coverage numbers. Do NOT use for first-time framework selection, broad test-stack migrations, or large production refactors.
harshitsinghbhandari/domain-expansion/skills/boundary-bug-hunter Skill
no license2★ repoAggressive user-flow and boundary-bug analysis on a diff or branch. Auto-detects entry points, traces flows through changed code, finds every seam (cross-module calls, serialization, file I/O, shared state, schema versioning, network/IPC), and refuses to mark the work complete until each unverified boundary has a real round-trip test or an explicit written out-of-scope record persisted in an audit file. Use whenever the user says "boundary check", "seam check", "round-trip check", "flow boundaries", "user-flow check", "before merge", "is this safe to ship", "pre-merge gate", "boundary bugs", "verify the joins", or asks to validate cross-module joins, producer/consumer contracts, or end-to-end coverage of a change. Also use as a final gate from pr-review on any diff that touches more than one file, module, or process. Be pushy. Most surviving production bugs live at seams, not inside units — if the diff crosses any boundary, this skill almost certainly applies.
harshitsinghbhandari/domain-expansion/skills/edge-case-hunter Skill
no license2★ repoExhaustive edge-case review that traces branching paths and boundary conditions in a diff or code sample and reports only unhandled cases. Use when the user asks to hunt edge cases, boundary conditions, missing guards, or wants an edge-case-focused review.
harshitsinghbhandari/domain-expansion/skills/pr-review Skill
no license2★ repoComprehensive PR review focusing on code quality, test coverage, security, backward compatibility, and what CI cannot check. Use when reviewing PRs, when asked to review code changes, or when the user mentions "review PR", "code review", or "check this PR".
harshitsinghbhandari/domain-expansion/skills/test-coverage-audit Skill
no license2★ repoComprehensive test suite audit that combines ruthless analysis with a solution-focused roadmap. Reads test suites (unit, integration, e2e) and source code, produces a brutal audit report of test quality and gaps, and generates prioritized testing improvements.
obielin/responsible-ai-skills/skills/fairness-testing Skill
2★ repoUse when writing tests for any ML model, classifier, or AI system that produces outputs affecting people. Fairness tests must be written before the model is used in production.
LittlePeter52012/skill-router/testdata/skills/test-skill-b Skill
2★ repoGoogle NotebookLM CLI integration. Use when user mentions NotebookLM, 笔记本LM, or wants to 查找/搜索 knowledge sources.
LittlePeter52012/skill-router/testdata/skills/test-skill-c Skill
2★ repoYou MUST use this before any creative work - creating features, building components, adding functionality.
The-AI-Directory-Company/agents-and-skills/skills/refactoring-checklist Skill
2★ repoSafe refactoring procedures with pre/post verification — covering scope assessment, test coverage checks, incremental transformation, and regression prevention.
The-AI-Directory-Company/agents-and-skills/skills/test-plan-writing Skill
2★ repoWrite risk-based test plans with coverage matrices, test level decisions, pass/fail criteria, and environment requirements — deciding what to test, at which level, and why.
kevinaimonster/skill-hub/skills/api-test Skill
no license2★ repoAPI 测试助手。帮用户编写 API 测试用例,生成测试脚本和 HTTP 请求。当用户说「API测试」「接口测试」「测试用例」「Postman」「curl命令」「HTTP请求」「接口怎么调」「api test」「接口调试」「mock数据」「压力测试」时触发。关键词:API测试、接口测试、HTTP请求、curl、Postman、REST、GraphQL、测试用例、mock、压力测试、负载测试、端到端测试、E2E、集成测试、API文档、Swagger、OpenAPI、HTTPie、请求头、状态码、认证、JWT、OAuth、接口调试、断言、自动化测试
kevinaimonster/skill-hub/skills/tdd Skill
no license2★ repo测试驱动开发助手。帮用户用 TDD 红-绿-重构工作流写高质量代码。当用户说「TDD」「测试驱动」「先写测试」「红绿重构」「test driven」「写个测试」「帮我 TDD」「测试先行」「write tests first」「red green refactor」时触发。关键词:TDD、测试驱动开发、红绿重构、Jest、Vitest、pytest、单元测试、测试先行、test driven development、red green refactor、先写测试再写代码、测试覆盖率
kevinaimonster/skill-hub/skills/unit-test Skill
no license2★ repo单元测试生成助手。帮用户编写单元测试、集成测试、Mock 设计、测试覆盖率提升。当用户说「帮我写单元测试」「写个测试用例」「怎么测这个函数」「mock怎么写」「测试覆盖率」「写测试」「unit test」「test case」「jest测试」「pytest」「vitest」「testing」时触发。关键词:单元测试、测试用例、测试覆盖率、mock、stub、spy、jest、pytest、vitest、mocha、junit、testing-library、断言、边界测试、异常测试、集成测试、e2e测试、测试驱动、代码覆盖率、coverage、test runner、describe、it、expect、assert、fixture、parametrize、测试金字塔
kevinaimonster/skill-hub/skills/user-research Skill
no license2★ repo用户研究助手。帮产品团队做用户画像、用户访谈、问卷设计、可用性测试方案。当用户说「帮我做用户研究」「用户画像」「用户访谈」「问卷设计」「可用性测试」「用户调研」「persona」「user interview」「user research」「usability test」「用户需求分析」「用户行为分析」「同理心地图」时触发。关键词:用户研究、用户画像、用户访谈、问卷设计、可用性测试、persona、用户调研、user research、user interview、usability testing、用户旅程、用户行为、需求分析、痛点分析、empathy map、同理心地图、A/B测试、用户反馈、NPS、用户满意度、焦点小组、卡片分类、五秒测试、场景分析、需求挖掘、定性研究、定量研究
teckedd-code2save/ai-build-tools/skills/api-test-generator Skill
2★ repoGenerates comprehensive API integration tests (using Jest/Supertest, Pytest, etc.) from existing backend repositories, ORM schemas, and router/controller files. Use when a user wants to test their newly provisioned data platform or backend services.
bcastelino/agent-skills-kit/skills/python-testing-patterns Skill
2★ repoImplement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
bcastelino/agent-skills-kit/skills/unit-testing-test-generate Skill
2★ repoGenerate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus. Use when writing test suites or improving test coverage.
jtsang4/efficient-coding/skills/test-driven-development Skill
2★ repoUse when implementing any feature or bugfix, before writing implementation code
The same file is in 33 other repositories
sssstwee/tastedistill/plugins/tastedistill/claude-skills/debug Skill
2★ repoDiagnose failures, broken behavior, regressions, test failures, runtime errors, stale state, rendering bugs, and repeated failed fixes. Use when something does not work, used to work, crashes, fails tests, or needs root-cause proof. Not for product planning or release readiness.
sssstwee/tastedistill/plugins/tastedistill/skills/tasted-debug Skill
2★ repoDiagnose failures, broken behavior, regressions, test failures, runtime errors, stale state, rendering bugs, and repeated failed fixes. Use when something does not work, used to work, crashes, fails tests, or needs root-cause proof. Not for product planning or release readiness.
ClarentCinematics/Codex-Skills-for-Enterprise/skills/ci-failure-triage Skill
2★ repoDiagnose failed CI runs, build logs, test output, deployment checks, or pipeline summaries and produce a root-cause hypothesis, reproduction path, likely owner, fix plan, and escalation guidance. Use when Codex needs to triage broken builds, flaky tests, failed checks, or release-blocking automation failures.
dzhokhov/markdown-agent-vault-ru/skills/test-gates Skill
2★ repoПрогон и верификация quality gates для задач разработки (скрипты/программы). Используй, когда нужно проверить изменение перед статусом «готово» или релизом: lint/type/static checks, unit/integration, smoke, flaky-policy и итоговый статус GREEN/YELLOW/RED. Триггеры: «прогони проверки», «проверь качество», «валидация», «smoke», «quality gates».
qiuy-collab/AutoFlow.skill/integrations/agent-skills/browser-testing-with-devtools Skill
2★ repoTests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
The same file is in 3 other repositories
qiuy-collab/AutoFlow.skill/integrations/superpowers/test-driven-development Skill
2★ repoUse when implementing any feature or bugfix, before writing implementation code
The same file is in 10 other repositories
qiuy-collab/AutoFlow.skill/integrations/webapp-testing Skill
2★ repoToolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
ralfyishere/rules-with-receipts/.claude/skills/debugging-playbook Skill
2★ repoDebug systematically instead of guessing - symptom, reproduction, hypotheses, discriminating tests, evidence, root cause, fix, regression test. Activate whenever something is broken, failing, wrong, or behaving unexpectedly - error messages, failing tests, crashes, wrong output, performance regressions, "it worked yesterday", "why is this happening", intermittent issues. Also applies to non-code failures: a report with wrong numbers, a workflow producing bad results, a prompt giving bad outputs.
llodev/skills/skills/ts-ddd-controller Skill
2★ repoCreate, review, or guide HTTP controllers in a TypeScript + DDD api. Use when the request involves `*.controller.ts` under `apps/api/src/<bc>/presentation/controllers/`, route definition, `ApiKeyGuard` on mutations, `ZodValidationPipe` against `@acme/<bc>-contracts` schemas, use case orchestration, mapping `Result` to HTTP via `mapResultToHttp`, signed-URL enrichment through a response mapper, HTTP status conventions (200/201/204), or controller tests using `@nestjs/testing` + `supertest` with an in-memory repository.
llodev/skills/skills/ts-ddd-domain-service Skill
2★ repoCreate, review, or guide pure Domain Service implementation in a TypeScript + DDD monorepo. Use when the request involves `*.service.ts` files inside `apps/api/src/<bc>/domain/services/`, domain policies, pure calculations/rules across multiple entities/VOs, naming patterns (`*Policy`, `*Calculator`, `*Resolver`, `*Specification`), branching on closed-set enums (status / kind / role) from `@acme/celebrations-contracts`, or tests in `apps/api/test/<bc>/domain/services/`. Scope is the *pure* domain layer; for orchestrators that need a repository or other I/O (e.g. `SlugAllocator`), see the sibling `application/services/` section at the end.
llodev/skills/skills/ts-ddd-entity Skill
2★ repoCreate, review, or guide Domain Entity implementation in a TypeScript + DDD codebase. Use when: the request touches `*.entity.ts` files under `apps/api/src/<bc>/domain/entities/` or their tests under `apps/api/test/<bc>/domain/entities/`; modeling business rules with `Entity` from `@acme/shared` (dual API `create`/`tryCreate`, `Result` / `Result.combine` validation); validating FK refs with `Id.required` or own id with `Id.tryCreate`; enforcing enum-backed closed-set fields (status / kind / layout / provider / palette) from `@acme/<bc>-contracts` instead of string literals; validating nested entities or arrays element-by-element; adding state transitions via `cloneWith` (leaf entity) or named domain methods like `publish`, `addSection`, `deactivate` that mutate `_field` + `touch()` (aggregate root); exposing typed getters or `toSnapshot()` for persistence boundaries.
llodev/skills/skills/ts-ddd-repository Skill
2★ repoCreate, review, or guide repository contracts and implementations in a TypeScript + DDD codebase. Use when the request involves `*.repository.ts` files under `apps/api/src/<bc>/domain/repositories/` or `apps/api/src/<bc>/infra/{firestore,memory}/`, persistence operations (save / findBy* / list*), the `<NAME>_REPOSITORY` DI token, adapting the Firebase Admin SDK to a domain port, `toFirestore`/`fromFirestore` mappers, the side-by-side Firestore + InMemory adapter pair, contract tests under `apps/api/test/<bc>/infra/{firestore,memory}/`, `Result` error handling, or CQRS Repository vs Query separation.
llodev/skills/skills/ts-ddd-use-case Skill
2★ repoCreate, review, or guide use case (application service) implementation in a TypeScript + DDD codebase. Use when the request involves `*.usecase.ts` files under `apps/api/src/<bc>/application/usecases/`, `application/services/<name>.service.ts` orchestrators, `UseCase<IN,OUT>` from `@acme/shared`, NestJS `@Injectable()` + `@Inject(<REPO_TOKEN>)` wiring, `Result.ok` / `Result.fail` / `withFail` / `Result.combine`, repository-port orchestration (`findBySlug`, `save`, `listByStatus`), aggregate state-transitions (`publish`, `addSection`), enum-typed inputs (`CelebrationKind`, `CelebrationStatusEnum.DRAFT`), or use-case tests under `apps/api/test/<bc>/application/usecases/` using `InMemoryCelebrationRepository`.
llodev/skills/skills/ts-ddd-value-object Skill
2★ repoCreate, review, or guide Value Object implementation in a TypeScript + DDD codebase. Use when the request involves 'value object', 'VO', `*.vo.ts` files (either shared at `libs/shared/src/vo/...` or BC-local at `apps/api/src/<bc>/domain/value-objects/...`), domain attribute validation/normalization, closed-set VOs derived from string enums (PaletteKey-style), composite-value VOs (ImageRef-style), `ValueObject` + `Result` pattern, `ValueObjectConfig`, `tryCreate`/`create` dual API, or VO test coverage.
subhansh-dev/agent-maxxing/engineering/testing-patterns Skill
2★ repoTesting methodology — what to test, how to test it, test structure, and common patterns.
rakibulism/agent-skills-os/skills/engineering-testing-strategy Skill
2★ repoDesign test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or test architecture.
The same file is in 51 other repositories
rakibulism/agent-skills-os/skills/test-writer Skill
2★ repoGenerate unit and integration tests for a given function, class, or module. Produces runnable tests in the project's existing test framework, covering happy path, edge cases, and error conditions. Use when the user asks to add tests, improve coverage, or write tests for new code.
rakibulism/agent-skills-os/skills/testing-strategist Skill
2★ repoDesigns a test strategy — coverage approach, test types, and test architecture for a feature or system. Use when asked "how should we test this" or for a test plan beyond just generating individual unit tests.
IamK77/Skill/skills/engineering/assay Skill
2★ repoPlan, write, and harden tests with a risk-driven decision tree: choose what to test, the right test type, the right test double, and the cases that actually catch bugs. Use when the user wants to test code; asks what or how to test a function, module, API, or system; mentions unit, integration, end-to-end, property-based, contract, or characterization tests, edge cases, mocks or fakes, flaky tests, or coverage; or says things like "help me test this", "what should I test", "write tests for X", or "I just fixed a bug".
IamK77/Skill/skills/engineering/gungnir Skill
2★ repoAttack your own system — under explicit authorization — to prove its defenses hold, before launch and continuously after: scope and authorize, recon, scan and enumerate, exploit and confirm real vulnerabilities (not scanner false positives), chain them into real impact, then report and re-test. The offensive half of the security pair (the spear) that proves what the `aegis` skill builds (the shield). Authorized, defensive penetration testing of systems you own or have written permission to test — never anything else. Use when the user wants to penetration-test their own application before launch, validate a fix actually closed a hole, stand up adversarial validation in CI or on a cadence, or learn to test for OWASP-class vulnerabilities on their own staging. Triggers on "pentest my app / attack my own system", "red-team my staging", "is this actually exploitable", "pre-launch security test".
IamK77/Skill/skills/engineering/husbandry Skill
2★ repoKeep a software system cheaply changeable over its whole life — the phase that is 60–80% of total cost and most under-resourced — across: classifying and funding it, making technical debt visible and paying it down, refactoring safely under test, defects to root cause, evolving versions/APIs/deps without breaking callers or hitting EOL, and legacy and retirement — tuned for a world where an agent reaches for a rewrite, incurs debt invisibly, refactors without a net, and rots docs. Use when the user is maintaining or evolving an existing system, tackling technical debt or a big-rewrite temptation, refactoring, triaging bugs, evolving a version/API/dependency, or working or retiring a legacy/EOL system. Triggers on "manage technical debt", "should we rewrite this", "refactor safely", "the codebase is a mess", "deprecate this API / semver", "upgrade this dependency", "legacy system with no tests", "characterization tests / strangler fig", "our docs are stale", "bus factor", "sunset / decommission this service".
IamK77/Skill/skills/inquiry/forge Skill
2★ repoThe experiment-run lens: turn the method that survived crucible into production code and RUN it to produce confirmation evidence — for any field that runs experiments to publish (ML, optimization, operations research, systems). Use when you are past method design and about to run the real experiments, or stress-testing a run plan. The one shift: the run is FROZEN and the agent's role switches from developer to OPERATOR — read and execute only, no write — because a coding agent optimizes "the test passed", not "the result is correct", and its shortest path to a passing validator is to edit it; and the governing standard is ONE-COMMAND REGENERATION — every table and figure rebuilds from raw results by one command. Triggers on "run the experiments", "harden / productionize the prototype", "set up the experiment pipeline", "make this reproducible / reproduction package", "organize my results", "my results don't match / numbers changed", "provenance / seeds / determinism", "cluster runs / resume".
IamK77/Skill/skills/surface/lookout Skill
2★ repoThe delivery-and-observability lens for a frontend build — where the suite's ethics becomes a launch gate. Use when setting up delivery/monitoring, shipping a metric-driven change, or running an A/B test. The mindset shift: shipping is not the finish line but the start of the conversation with reality — so every change is made instantly visible and the real world is instrumented; and the moment the metrics dashboard is born it pulls every decision, so the objective function and guardrails from bearings come back here for their exam. A/B testing is a gradient-descent optimizer: aimed at an engagement metric over a human nervous system it DISCOVERS manipulation as a local optimum — the real villain is the loss function. Triggers on "deploy / CI/CD / preview deploys", "feature flags / progressive rollout / canary", "observability / monitoring / RUM / Web Vitals", "analytics / event tracking", "A/B test / experiment", "which metric should we optimize", "is this metric / experiment ethical", "dark pattern".
IamK77/Skill/skills/surface/pilot Skill
2★ repoNavigate the surface frontend suite: route a frontend task to the right skill — and, because the suite is a lifecycle, to the right ENTRY STAGE — or to a sibling suite, or say plainly when none is warranted. The un-gated front door to the seven surface skills (bearings, keel, wellspring, seaworthy, trials, lookout, bulwark). Use when starting or mid-way through frontend work, unsure which stage fits or whether the suite is needed. The shift it leans on: most frontend work is NOT greenfield, so the best routing names WHERE IN THE PIPELINE TO ENTER, not stage 0. Triggers on "which frontend skill / where do I start", "how should I build this UI / app", "my state is a mess / it's out of sync", "it feels janky / slow", "my component tests break on every refactor", "dark pattern / which metric", "the frontend is rotting as it grows". It also redirects ACROSS suites: code craft / architecture / testing / process / security → engineering; realtime / offline / CRDT → distributed; library choice → quarry.
IamK77/Skill/skills/surface/trials Skill
2★ repoThe correctness lens for a frontend build, organized around one question that decides whether your test suite is a safety net or a straitjacket: does this test go red when BEHAVIOR changes (a net — it warns on real regressions) or when the IMPLEMENTATION changes (a shackle — it reddens on every refactor, so you fix tests instead of code, and learn to ignore red). Use after seaworthy's slices exist, when writing or auditing frontend tests, or when a suite is brittle. The one shift: test BEHAVIOR, not internal structure — and put the test budget where frontend bugs actually cluster (integration: the seams, the two-graph drift, state out of sync), which makes the right shape a TESTING TROPHY, not the classic pyramid. Triggers on "what / how should I test this UI", "unit vs integration vs E2E", "testing-library / Playwright / Cypress / Vitest / Jest", "my tests break on every refactor", "snapshot tests", "should I mock this", "test coverage / 100%", "is this test worth keeping", "flaky tests".
F-e-u-e-r/opus-pack/skills/ground-truth-gates Skill
2★ repoBuild executable verification gates (golden set, replay corpus, project checks) so "it works" becomes a checked fact instead of a claim. Load when changing any LLM-judgment step (classify/extract/route/prompt), refactoring logic that processes real logged data, designing tests for a fix, setting up a commit/ship gate for a project, designing a runtime guard (a hook, validator, or auth check) and its fail direction, or when you are about to trust a passing test that has never been shown able to fail. Also the reference for what "proof gate" means in delegation-and-review packets. Do NOT load for one-off scripts or exploratory spikes — plain operational-rigor covers those.
AIKUSAN/minecraft-agent-skills-bundle/.agents/skills/minecraft-testing Skill
2★ repoWrite automated tests for Minecraft mods and plugins for 1.21.x. Covers NeoForge GameTests (@GameTest annotation, GameTestHelper assertions, test structure placement), Fabric game tests (fabric-gametest-api-v1), unit testing non-Minecraft logic with JUnit 5, MockBukkit for Paper/Bukkit plugin testing (mock server, mock player, event dispatching, inventory checking), integration testing with a test server via Gradle, and GitHub Actions CI workflows that run GameTests headlessly. Includes patterns for mocking registries, testing event handlers, testing commands, and test-driven development for Minecraft projects. Use when the user asks about testing Minecraft mods or plugins, writing GameTests, setting up MockBukkit, or configuring CI for Minecraft projects.
AIKUSAN/minecraft-agent-skills-bundle/.codex/skills/minecraft-testing Skill
2★ repoWrite automated tests for Minecraft mods and plugins for 1.21.x. Covers NeoForge GameTests (@GameTest annotation, GameTestHelper assertions, test structure placement), Fabric game tests (fabric-gametest-api-v1), unit testing non-Minecraft logic with JUnit 5, MockBukkit for Paper/Bukkit plugin testing (mock server, mock player, event dispatching, inventory checking), integration testing with a test server via Gradle, and GitHub Actions CI workflows that run GameTests headlessly. Includes patterns for mocking registries, testing event handlers, testing commands, and test-driven development for Minecraft projects. Use when the user asks about testing Minecraft mods or plugins, writing GameTests, setting up MockBukkit, or configuring CI for Minecraft projects.
AIKUSAN/minecraft-agent-skills-bundle/plugins/minecraft-codex-skills/skills/minecraft-testing Skill
2★ repoWrite automated tests for Minecraft mods and plugins for 1.21.x. Covers NeoForge GameTests (@GameTest annotation, GameTestHelper assertions, test structure placement), Fabric game tests (fabric-gametest-api-v1), unit testing non-Minecraft logic with JUnit 5, MockBukkit for Paper/Bukkit plugin testing (mock server, mock player, event dispatching, inventory checking), integration testing with a test server via Gradle, and GitHub Actions CI workflows that run GameTests headlessly. Includes patterns for mocking registries, testing event handlers, testing commands, and test-driven development for Minecraft projects. Use when the user asks about testing Minecraft mods or plugins, writing GameTests, setting up MockBukkit, or configuring CI for Minecraft projects.
bogdanbaciu21/skills/table-system-migration Skill
2★ repoAudit, migrate, and regression-test table systems across content-heavy websites, blogs, documentation sites, and admin surfaces. Use when Codex needs to normalize many ad hoc HTML table styles into a canonical table component, preserve legacy/admin table behavior, build a no-new-violations ratchet, add real-browser CSS regression coverage for table layout, or prepare a public-safe writeup/skill from a private table cleanup.
jukrap/ai-agent-playbook/skills/delivery/flaky-test-triage Skill
2★ repoUse when diagnosing, reproducing, stabilizing, quarantining, or documenting flaky, nondeterministic, timing-dependent, or intermittent tests.
jukrap/ai-agent-playbook/skills/delivery/test-fixture-data-design Skill
2★ repoUse when designing, reviewing, or repairing test fixtures, factories, mocks, seeds, snapshots, golden files, sample payloads, test databases, or fixture maintenance boundaries.
jukrap/ai-agent-playbook/skills/delivery/test-verification-strategy Skill
2★ repoUse when planning, reviewing, or repairing verification strategy, test scope, contract/manual checks, coverage gaps, risk-based selection, or release confidence.
jukrap/ai-agent-playbook/skills/devops/ci-failure-triage Skill
2★ repoUse when diagnosing failing CI jobs, build pipelines, deployment checks, flaky tests, environment drift, or release automation failures.
jukrap/ai-agent-playbook/skills/frontend/visual-regression-qa Skill
2★ repoUse when checking screenshots, responsive breakpoints, layout overflow, clipping, visual diffs, font/text fit, canvas/media rendering, or browser-rendered UI regressions.
osseous/skills/skills/unreal-engine-angelscript Skill
2★ repoAuthor Hazelight AngelScript (.as) gameplay code for Unreal Engine 5.x projects using the Hazelight UnrealEngine-Angelscript fork. AngelScript looks like UE C++ but differs in load-bearing ways — no `#include`, no `GENERATED_BODY`, `default` keyword for sub-object config, `float` is 64-bit, RPCs are reliable by default, no `GetLifetimeReplicatedProps`, no `UInterface` support. This skill mandates consulting `angelscript.hazelight.se` and grepping the project `Script/` directory before claiming any binding exists. Use when adding/editing any `.as` file, subclassing a C++ UCLASS in script, wiring replication, writing tests (`Test_*` / `IntegrationTest_*`), or migrating logic from C++ to AngelScript.
ainova-systems/intelligence-dev-packs/packs/core/skills/dev-run-tests Skill
2★ repoRun typecheck, lint, and tests with the right scope; analyze failures
knowhowlab/agent-testkit/skills/test-manual Skill
2★ repoConduct the repository's TESTS_MANUAL.md plan as a guided manual test — the USER runs every command and GUI action while Claude presents one step at a time, evaluates reported results, proposes (never applies unasked) fixes, and keeps the protocol file. Use when the user wants to test by hand, run commands themselves, do a guided walkthrough or acceptance session, or verify the app manually — with optional scope arguments.
rumotion/ai-agent-project-template/.agents/skills/test-strategist Skill
2★ repoDesigns test strategy for new features, bug fixes, refactors, and risky changes. Use when deciding what tests to add or run.
rumotion/ai-agent-project-template/.cline/skills/test-strategist Skill
2★ repoDesigns test strategy for new features, bug fixes, refactors, and risky changes. Use when deciding what tests to add or run.
14790897/my-skills/skills/electron-e2e-cdp-testing Skill
no license2★ repoElectron 34+ 桌面应用端到端测试技能。当需要为 Electron 应用编写或调试 E2E 测试、遇到 Playwright _electron.launch 不可用、CI 中 Chromium SIGTRAP 崩溃、ELECTRON_RUN_AS_NODE 导致 Electron 以 Node 模式运行、或需要 CDP 远程调试连接方案时使用此技能。涵盖 CDP 连接、进程管理、跨平台 kill、CI sandbox 处理、concurrency 策略。适用于 Electron 34 及以上版本。