Test

Proves a code change works: runs every repository check until green, then proves each acceptance criterion with tests, and by running the real app for anything a user can see or call. Use to test or verify a diff, branch, PR, URL, or user flow.

434 stars 73 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add owainlewis/blueprint --skill test
Manual install
git clone --depth 1 https://github.com/owainlewis/blueprint.git /tmp/blueprint
mkdir -p ~/.claude/skills
cp -r /tmp/blueprint/skills/test ~/.claude/skills/test

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Test

Show that each acceptance criterion passes. Reading the code is not proof.

## Steps

1. Run every check the repository has: format, lint, typecheck, and tests. The commands are in `AGENTS.md`, `CLAUDE.md`, the README, or the project's scripts. Fix what the change broke and run them all again. After three rounds on the same failure, stop and report it.
2. List each acceptance criterion (`AC-n`, `J-n`, `REQ-n`, `INV-n`) from the ticket, word for word.
3. Point each criterion to a test that proves it. Where none exists, write one that calls the public interface. Revert the code once to confirm the main new test fails.
4. If a user can see or call the change, run the real app the way they would. Use the repository's own end-to-end tests or scripts if it has them. Otherwise use a real browser for a web page, a terminal for a command-line tool, and HTTP requests for an API.
5. For a web page, check desktop and mobile widths, keyboard use, and console errors.
6. Save the evidence for the PR: screenshots, terminal output, or responses.

## Return

Failures and unverified criteria first:

```text
Criterion: <ID or exact wording>
Result: Pass / Fail / Unverified
Evidence: <command, user flow, screenshot, or captured output>
```

Then each check command you ran and its result.

Fix the code, not the test. Report failures the change did not cause; leave them alone.
Read the full skill on GitHub

Details

Skill name
test
Path
skills/test/SKILL.md
License
MIT
Repo updated
10 November 2026

FAQ

What does the Test skill do?

Proves a code change works: runs every repository check until green, then proves each acceptance criterion with tests, and by running the real app for anything a user can see or call. Use to test or verify a diff, branch, PR, URL, or user flow.

How do I install the Test skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add owainlewis/blueprint --skill test. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Test popular?

It lives in owainlewis/blueprint, which has 434 GitHub stars and 73 forks.

Related skills

Architecture

434

owainlewis/blueprint

Writes root ARCHITECTURE.md from a fixed template: the intended system, a data flow diagram, the data model, and the rules every feature must follow. Use for a new system or a change to its boundaries, data, or deployment.

Software Development73

Architecture Review

434

owainlewis/blueprint

Reviews a technical proposal before any code is written: an architecture, spec, RFC, ADR, or design issue. Finds choices that would make it wrong, unsafe, or impossible to prove, and the open questions that block building it.

Software Development73

Codex Issue Coordinator

434

owainlewis/blueprint

Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.

Software Development73

Test Specialist

473

ailabs-393/ai-labs-claude-skills

This skill should be used when writing test cases, fixing bugs, analyzing code for potential issues, or improving test coverage for JavaScript/TypeScript applications. Use this for unit tests, integration tests, end-to-end tests, debugging runtime errors, logic bugs, performance issues, security vulnerabilities, and systematic code analysis.

Testing & QA117

TDD Workflow

335

zhukunpenglinyutong/ai-max

在编写新功能、修复 bug 或重构代码时使用此 skill。强制执行测试驱动开发,覆盖率要求 80% 以上,包括单元测试、集成测试和 E2E 测试。

Testing & QA37

Test Skill

291

joshuadavidthomas/opencode-agent-skills

A test skill to verify all plugin tools work correctly - use_skill, read_skill_file, run_skill_script, find_skills

Testing & QA32

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.