Testing

Unit tests, integration tests, test automation

Showing 1657-1680 of 6726 skills
jmagly

gate-evaluation

by jmagly

Validator agents: agents/

Code Review 225 10mo ago
jmagly

sdlc-reports

by jmagly

Dashboard guide: docs/dashboard-configuration.md

Analytics 225 10mo ago
jmagly

Auto-Provenance

by jmagly

@.claude/rules/qualified-references.md - Qualified reference rules

Agents 225 8mo ago
jmagly

regression-auto-baseline

by jmagly

@.claude/rules/executable-feedback.md - Executable feedback rules

Git & VCS 225 8mo ago
OpenAgentsInc

nostr

by OpenAgentsInc

How Nostr works in this repository: the three NIP lanes under nips/, the wire protocol (NIP-01), relay authentication (NIP-42), payload encryption (NIP-44), the Block agent NIPs the relay serves, and the OpenAgents NIPs (NIP-CJ jobs, NIP-CAP capabilities, NIP-PRG programs) that carry a Coder turn to a worker. Read it before touching crates/nostr, crates/nostr-relay, crates/coder-runtime/src/relay.rs, coder-worker, or any file under nips/, and before debugging a relay handoff.

Git & VCS 458 6d ago
NeverSight

specalign

by NeverSight

Align spec files with implementation. Detects drift between spec and code, surfaces discrepancies, user decides whether to update spec or code. Use when both a spec file and its implementation are in context.

Code Review 219 8mo ago
NeverSight

playwright-best-practices

by NeverSight

Provides Playwright test patterns for resilient locators, Page Object Models, fixtures, web-first assertions, and network mocking. Must use when writing or modifying Playwright tests (.spec.ts, .test.ts files with @playwright/test imports).

Processing 219 9mo ago
NeverSight

e2e

by NeverSight

Run e2e tests, fix flake and outdated tests, identify bugs against spec. Use when running e2e tests, debugging test failures, or fixing flaky tests. Never changes source code logic or API without spec backing.

API Dev 219 8mo ago
r-lib

tidy-deprecate-function

by r-lib

Guide for deprecating R functions/arguments. Use when a user asks to deprecate a function or parameter, including adding lifecycle warnings, updating documentation, adding NEWS entries, and updating tests.

Code Gen 943 9mo ago
NeverSight

data-driven-testing

by NeverSight

"DEPRECATED: Use testing-best-practices instead. This skill has been retired."

Code Review 219 8mo ago
NeverSight

specalign

by NeverSight

Align spec files with implementation. Detects drift between spec and code, surfaces discrepancies, user decides whether to update spec or code. Use when both a spec file and its implementation are in context.

Code Review 219 8mo ago
NeverSight

data-driven-testing

by NeverSight

"DEPRECATED: Use testing-best-practices instead. This skill has been retired."

Code Review 219 8mo ago
duc01226

feature-docs

by duc01226

Use when the user asks to generate comprehensive feature documentation with verified test cases, create feature README with code evidence, or document a complete feature with test verification. Triggers on keywords like "feature documentation", "document feature", "comprehensive docs", "feature README", "test verification", "verified documentation".

Code Gen 6 9mo ago
NeverSight

e2e

by NeverSight

Run e2e tests, fix flake and outdated tests, identify bugs against spec. Use when running e2e tests, debugging test failures, or fixing flaky tests. Never changes source code logic or API without spec backing.

API Dev 219 8mo ago
NeverSight

testing-best-practices

by NeverSight

Test layering, execution, and CI guidance across unit, integration, and e2e. Use when designing tests, writing test cases, or planning test strategy for a module.

Debugging 219 8mo ago
NeverSight

atomise

by NeverSight

"Atom of Thoughts (AoT) reasoning - decompose complex problems into atomic units with confidence tracking and backtracking. For genuinely complex reasoning, not everyday questions. Triggers on: atomise, complex reasoning, decompose problem, structured thinking, verify hypothesis."

Security 219 9mo ago
NeverSight

playwright-best-practices

by NeverSight

Provides Playwright test patterns for resilient locators, Page Object Models, fixtures, web-first assertions, and network mocking. Must use when writing or modifying Playwright tests (.spec.ts, .test.ts files with @playwright/test imports).

Processing 219 9mo ago
mastepanoski

ai-assessment-scale

by mastepanoski

Evaluate AI contribution in projects using the AI Assessment Scale (AIAS) 5-level framework. Measure AI involvement from no AI to full AI exploration across development stages.

Code Review 59 8mo ago
Dicklesworthstone

Complete Rust Development

by Dicklesworthstone

A comprehensive skill for Rust development that combines error handling, testing, and logging patterns. Demonstrates the 'includes' composition feature by merging content from multiple standalone skills.

Processing 207 9mo ago
faionfaion

faion-javascript-developer

by faionfaion

"JavaScript/TypeScript: React, Node.js, Next.js, modern JS patterns."

Testing 4 8mo ago
faionfaion

faion-ba-modeling

by faionfaion

"BA Modeling: Use cases, user stories, process models (BPMN), data models, decision tables, interfaces, acceptance criteria. 7 methodologies."

Processing 4 8mo ago
tovimx

maestro-mobile-testing

by tovimx

"Maestro mobile E2E testing patterns for React Native/Expo apps: YAML test flows, testID selectors, adaptive auth state, optimistic update verification, GraalJS scripting, cross-platform stability, CI/CD integration, Maestro Cloud, and MCP server integration"

API Dev 27 8mo ago
antinomyhq

resolve-conflicts

by antinomyhq

Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.

File Ops 7.6K 11mo ago
antinomyhq

create-pr-description

by antinomyhq

Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it.

Code Gen 7.6K 9mo ago