optimizespec-verify
Verify an OptimizeSpec self-improvement implementation. Use when checking generated skills, artifact completeness, eval runner behavior, ASI quality, direct…
Skills
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 10-30 00:12
Testing & quality
12,904 results
disciplined-validation
Phase 5 of disciplined development. Validates system against original requirements through system testing and user acceptance testing (UAT). Uses structured…
disciplined-verification
Phase 4 of disciplined development. Verifies implementation against design through unit and integration testing. Builds traceability matrices, tracks coverage,…
quality-gate
Right-side-of-V verification/validation orchestration for a change or PR. Produces a single Quality Gate Report with evidence covering: code review, security…
testing
Comprehensive test writing, execution, and failure analysis. Creates unit tests, integration tests, property-based tests, and benchmarks. Analyzes test…
generate-test-cases
Generate test cases and checklists for software testing. Use this skill whenever the user asks to create test cases, test scenarios, test plans, checklists, QA…
performance-budget
Use when reviewing CI configuration, bundle analysis workflows, or pull requests that add dependencies and assets. Distinguish bundle-size budgets from runtime…
screen-reader-testing
Use when performing accessibility audits of web pages, components, or full user flows. Applies to all web content accessed via assistive technology.…
ui-testing-harness
This skill should be used when testing or debugging an agent UI locally — the basic-host loop, MCP Inspector, cloudflared tunnels into Claude or ChatGPT,…
python-testing-conventions-taudelta
Use when writing or restructuring Python tests — deciding how much duplication a test should carry before it stops being readable, what a fixture should cover…
code-review
Systematic code review: security checks, performance analysis, complexity assessment, best practice validation, and review checklists.
agent-test-generator
Specialist subagent: Generates comprehensive test suites using TDD patterns. Use only when the user explicitly asks for tests, improved coverage, or test-first development.
manual-testing
Run a session-based manual test of the project's running app in one of five modes: exploratory, verification, smoke, assessment (UX, localization,…
editor-harvest-plan
Turn an editor-test-harvester report into one lane-specific execution plan, e.g. process every Slate v2 candidate from a harvest through slate-plan without…
editor-test-harvester
Mine external editor repositories for portable editor-behavior tests with ClawSweeper-style discipline: multi-pass exhaustive inventory, confidence scoring,…
slate-ar-recipe
Slate v2 Autoresearch recipe picker. Lists/recommends Codex Autoresearch recipes, produces read-only setup plans, and maps non-perf loops such as test runtime,…
setup-visual-testing
Set up UI Verify visual regression testing in a repo end to end — detect or scaffold the capture path (Storybook stories, a Playwright suite, or Vitest…
adapt-framework
Adapt this boilerplate's KATA test architecture, auth, schemas, variables, fixtures, CI, MCPs, and reporting to a project already reverse-engineered by…
business-api-context
What the API of the system under test MEANS to the business: every endpoint group, who calls it and why, what it changes, which auth level and role it needs,…
business-domain-context
The vocabulary and the business of the system under test: what the product is for, who pays and why, and what every domain term means (the business meaning,…
business-e2e-context
How people actually use the system under test end to end: the personas, the user journeys first (entry point, steps, branches, where money or data changes…
test-framework-adaptation
Adapt this boilerplate's KATA test architecture, auth, schemas, variables, env schema, fixtures, CI, MCPs, and reporting to a project already…
test-driven-development
Red-Green-Refactor workflow: write tests before implementation, maintain coverage. Use when implementing logic, fixing bugs, or changing behavior.
condition-based-waiting
Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for…