Verify
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
$ npx promptcreek add verifyAuto-detects your installed agents and installs the skill to each one.
What This Skill Does
This skill automates the verification process for a React codebase, ensuring code quality and consistency. It runs code formatting, linting, type checking, and tests across different environments. It's intended for developers seeking to streamline their workflow and catch issues early.
When to Use
- Before submitting a pull request.
- As a pre-commit hook to prevent broken code.
- To ensure code style consistency across the team.
- To catch type errors and runtime exceptions early.
- To validate changes against different React environments.
- After merging code to the main branch.
Key Features
Installation
$ npx promptcreek add verifyAuto-detects your installed agents (Claude Code, Cursor, Codex, etc.) and installs the skill to each one.
View Full Skill Content
Verification
Run all verification steps.
Arguments:
- $ARGUMENTS: Test pattern for the test step
Instructions
Run these first in sequence:
- Run
yarn prettier- format code (stop if fails) - Run
yarn linc- lint changed files (stop if fails)
Then run these with subagents in parallel:
- Use
/flowto type check (stop if fails) - Use
/testto test changes in source (stop if fails) - Use
/test wwwto test changes in www (stop if fails)
If all pass, show success summary. On failure, stop immediately and report the issue with suggested fixes.
Supported Agents
Attribution
Details
- License
- MIT
- Source
- admin
- Published
- 3/18/2026
Tags
Related Skills
Agent Protocol
Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
Agent Workflow Designer
Agent Workflow Designer
CTO Advisor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.