TDD Workflow
hellangleZ/burn-in-cceverywhere-ralph
A skill your agent uses when writing new features, fixing bugs, or refactoring code.
Behavioral verification rules for claiming a change works. An agent skill from web-infra-dev/rstest.
Install Verify
$ npx skills add web-infra-dev/rstest --skill verify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install web-infra-dev/rstest verify --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/web-infra-dev/rstest.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/verify .claude/skills/verify && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "verify" agent skill from https://github.com/web-infra-dev/rstest/tree/main/.agents/skills/verify into .claude/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/web-infra-dev/rstest/tree/main/.agents/skills/verifyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add web-infra-dev/rstest --skill verify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install web-infra-dev/rstest verify --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/web-infra-dev/rstest.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/verify .agents/skills/verify && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verify" agent skill from https://github.com/web-infra-dev/rstest/tree/main/.agents/skills/verify into .agents/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add web-infra-dev/rstest --skill verify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install web-infra-dev/rstest verify --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/web-infra-dev/rstest.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/verify .cursor/skills/verify && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "verify" agent skill from https://github.com/web-infra-dev/rstest/tree/main/.agents/skills/verify into .cursor/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/web-infra-dev/rstest.git --path .agents/skills/verify--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add web-infra-dev/rstest --skill verify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install web-infra-dev/rstest verify --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/web-infra-dev/rstest.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/verify .gemini/skills/verify && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "verify" agent skill from https://github.com/web-infra-dev/rstest/tree/main/.agents/skills/verify into .gemini/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install web-infra-dev/rstest verifyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add web-infra-dev/rstest --skill verify -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/web-infra-dev/rstest.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/verify .github/skills/verify && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "verify" agent skill from https://github.com/web-infra-dev/rstest/tree/main/.agents/skills/verify into .github/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add web-infra-dev/rstest --skill verify -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install web-infra-dev/rstest verify --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/web-infra-dev/rstest.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/verify .opencode/skills/verify && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "verify" agent skill from https://github.com/web-infra-dev/rstest/tree/main/.agents/skills/verify into .opencode/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
verify- GitHub stars
- 505
- Token cost
- ~1.2k tokens
- SKILL.md length
- 576 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT
At a glance
Behavioral verification rules for claiming a change works. An agent skill from web-infra-dev/rstest.
- Works in 4 steps: Start from fresh build state. E2E and… → Drive the real binary on the smallest… → Observe the output, not the summary.… → …
- Tasks that involve Unit testing
- SKILL.md covers Forbidden proxies, The observation loop, What to observe, by change shape and False-signal gotchas
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Verify is an agent skill from web-infra-dev/rstest. Behavioral verification rules for claiming a change works. Use before reporting any fix/feature as done, when tempted to conclude from typecheck or unit-test results alone, when deciding what evidence a change needs, or when a test result looks suspicious (stale build, flaky pass, snapshot churn).
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Unit testing. The repository describes itself as: The JavaScript testing framework powered by Rspack. The licence is MIT.
When your agent uses it
- Tasks that involve Unit testing
Example prompts
- “/verify”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Start from fresh build state. E2E and fixture runs consume built output; if a result contradicts your expectation, suspect a stale or…
- Drive the real binary on the smallest repro. Run the actual rstest CLI the way a user would — an e2e fixture, not an import of internal…
- Observe the output, not the summary. Read the reporter output for the specific behavior you changed, and check the exit code (echo $?)…
- Observe both directions when feasible. See the broken behavior without your change and the fixed behavior with it — a fix you never saw…
What it can do on your machine
Read from SKILL.md and the folder at commit d56bf97. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Verify loads about 1.2k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 576 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from web-infra-dev/rstest at commit d56bf97, republished under its MIT licence (© web-infra-dev). 576 words, ~1,173 tokens.
Download SKILL.mdSave it as
.claude/skills/verify/SKILL.md (or your agent's skills folder).- name
- verify
- description
- Behavioral verification rules for claiming a change works. Use before reporting any fix/feature as done, when tempted to conclude from typecheck or unit-test results alone, when deciding what evidence a change needs, or when a test result looks suspicious (stale build, flaky pass, snapshot churn).
- metadata.internal
- true
Verify Behavior, Not Proxies
A change is verified only when you have observed the real behavior change — the actual CLI output, reporter output, or exit code — not when a proxy signal went green. This skill owns exactly one concern: what counts as evidence. How to run things lives in the testing skill; what work a change requires (including the Flip-and-Verify regression protocol) lives in the development skill — don't expect commands or checklists here.
Forbidden proxies
None of these, alone, justify claiming a behavioral change works:
- Typecheck / lint green. Proves the types compose, not that the behavior changed.
- Unit tests green. They exercise source via the workspace runner, not the built CLI → runner → reporter pipeline users run.
- "My new test passes." A test that passes both before and after the fix proves nothing — it must flip (protocol:
development→ Flip-and-Verify). - "The code path is clearly hit." Reading the code and reasoning that it must work is prediction, not observation.
- Snapshot updated with
-u. Regeneration makes tests green by definition; green-after-update is not evidence (update policy:testing→ Snapshot policy). - Build succeeded. Compiling is not running.
- A tool accepted your config. Silently-ignored options look identical to working ones — prove the rule/option fires by observing it reject or change something (inject a violation, toggle the option).
If verification is genuinely impossible (needs real CI, a specific OS, a headed browser you can't run), say so explicitly instead of substituting a proxy.
The observation loop
- Start from fresh build state. E2E and fixture runs consume built output; if a result contradicts your expectation, suspect a stale or half-finished build before suspecting the code (rebuild procedure:
testing→ Rebuild before E2E). - Drive the real binary on the smallest repro. Run the actual
rstestCLI the way a user would — an e2e fixture, not an import of internal functions (run forms:testing→ Running tests). - Observe the output, not the summary. Read the reporter output for the specific behavior you changed, and check the exit code (
echo $?) when the change affects pass/fail semantics. - Observe both directions when feasible. See the broken behavior without your change and the fixed behavior with it — a fix you never saw fail is unverified.
Show full SKILL.md (213 more words)Show less
What to observe, by change shape
| Change touches | Minimum real observation |
|---|---|
| Core runtime / runner / pool | A targeted e2e run plus its exit code, on a fixture that exercises the changed behavior |
| Reporter / console output | The actual stdout/stderr the CLI prints, not just assertion results |
| CLI flags / config options | Two runs — with and without the option — confirming the behavior differs |
| Browser mode | A browser e2e run (headless is the default; see testing → Browser E2E) |
| Adapters (rsbuild / rslib / rspack) | A fixture run through the adapter, confirming the transformed config takes effect at runtime |
| Coverage providers | The emitted report content, not just "the run succeeded" |
| Watch mode | An actual watch session reacting to a file change, not a one-shot run |
| Lint rules / hooks / gates | The gate firing on an injected violation with the intended message, then passing when clean |
False-signal gotchas
- A pass on re-run after a fail may be flakiness, not a fix. Re-run the exact failing command; if results alternate with no code change, report it as flaky rather than fixed.
- Inexplicable fixture behavior is usually stale state, not logic — stale
dist, persistent fixture output, shared cwd (mechanisms and cleanup:testing). - Absence of a failure is weak evidence. "It didn't error" only counts if you confirmed the run actually reached the changed code path.
© web-infra-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/verify of web-infra-dev/rstest.
Open the folder on GitHubat commit d56bf97
Compare with similar skills
Verify next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Verify this skillweb-infra-dev/rstest | 505 | — | ~1.2k | Automated safety check: Pass | MIT | |
| TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph | 112 | 11 repos | ~2.4k | Automated safety check: Pass | None | |
| Testing OpenLogi UIAprilNEA/OpenLogi | 23k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Go Testingcxuu/golang-skills | 170 | 1 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Contractssamchon/nestia | 2.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Cohesion Over TestabilityEpicenterHQ/epicenter | 4.8k | — | ~2k | Automated safety check: Pass | Custom licence |
Similar skills
Testing OpenLogi UI
AprilNEA/OpenLogi
Verifies OpenLogi's native GPUI interface with focused tests, the component gallery and a mock agent, choosing the evidence that fits each change.
Go Testing
cxuu/golang-skills
A skill your agent uses when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff.
Contracts
samchon/nestia
Defines self-acknowledgments for production declarations and tests.
Cohesion Over Testability
EpicenterHQ/epicenter
Collapse test-shaped production boundaries while preserving behavior and coverage.
JS-in-HTML Testing
liaohch3/claude-tap
Tests JavaScript embedded in an HTML file in two layers: pytest checks of the logic ported to Python, and Playwright runs in a real browser for the DOM.
More from web-infra-dev/rstest
All 9 skills in this repoCreate Draft Release Notes
web-infra-dev/rstest
Create or update draft GitHub release notes, or output organized Markdown when draft creation is unavailable.
Create Release Blog
web-infra-dev/rstest
Generate a narrative version release blog post from commits within a tag range.
API Doc Sync
web-infra-dev/rstest
Verify hand-written API doc signatures match the exported types.
Testing
web-infra-dev/rstest
Testing workflow for the Rstest monorepo. An agent skill from web-infra-dev/rstest.
Typescript
web-infra-dev/rstest
TypeScript anti-slop guardrails. An agent skill from web-infra-dev/rstest.
Development
web-infra-dev/rstest
Feature and bug-fix development checklist for the Rstest monorepo.
Related
Categories
Questions about Verify
What does Verify do?
Behavioral verification rules for claiming a change works. An agent skill from web-infra-dev/rstest. Verify is an agent skill from web-infra-dev/rstest. Behavioral verification rules for claiming a change works.
When should I use Verify?
Verify fits situations like: tasks that involve Unit testing.
How do I install Verify in Claude Code?
Run `npx skills add web-infra-dev/rstest --skill verify -a claude-code`. Or copy the skill folder (.agents/skills/verify in web-infra-dev/rstest) into .claude/skills/verify in your project. Claude Code loads it when a task matches its description.
How do I install Verify in Codex?
Run `npx skills add web-infra-dev/rstest --skill verify -a codex`. Or copy the skill folder (.agents/skills/verify in web-infra-dev/rstest) into .agents/skills/verify in your project. Codex loads it when a task matches its description.
Can I use Verify in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add web-infra-dev/rstest --skill verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify, .gemini/skills/verify, .github/skills/verify and .opencode/skills/verify in your project.
What does Verify need to run?
SKILL.md names no scripts, command-line tools or credentials: Verify is instructions for the agent only.
Does Verify access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Verify safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Verify use?
Verify is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Verify use?
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Verify?
Skills that share tags, products or a category with Verify: TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars), Testing OpenLogi UI (AprilNEA/OpenLogi, 23k stars), Go Testing (cxuu/golang-skills, 170 stars) and Contracts (samchon/nestia, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verify?
web-infra-dev (a GitHub organization) maintains it in web-infra-dev/rstest, which has 505 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on September 30, 2026.
Source: web-infra-dev/rstest on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.