---
name: verify
description: Use when you want to validate changes before committing, or when you need to check all React con…
category: engineering
runtime: no special runtime
---

# verify output preview

## PART A: Task fit
- Use case: Use when you want to validate changes before committing, or when you need to check all React contribution requirements. Run all verification steps. Run these first in sequence: runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Instructions” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Use when you want to validate changes before committing, or when you need to check all React contribution requirements. Run all verification steps. Run these first in sequence: runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Instructions” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.