Verification

VerifiedCaution

Validate changes before committing by running formatting, linting, type checking, and tests.

Sby Skills Guide Bot
TestingIntermediate
7/22/2026
Claude Code
#pre-commit#react#linting#type-checking#test-runner

Recommended for

Automated summary

Runs the full React contribution verification suite (Prettier, lint, Flow, source and www tests) before committing.

Strengths

  • Chains formatting and linting sequentially with an immediate stop on failure, then runs the heavier checks in parallel through subagents
  • Covers both the source tree and the www directory so no test scope is silently skipped
  • Reports the failure with suggested fixes rather than continuing silently

Limitations

  • Tightly coupled to the React repo: relies on yarn prettier, yarn linc, /flow and /test
  • No way to narrow or relax individual steps, apart from the test pattern passed as an argument
  • Requires a harness that can spawn subagents and invoke the /flow and /test slash commands
When to use it

Use it right before committing or opening a pull request in the React repository, to validate every contribution requirement at once.

When not to use it

Avoid it on projects that do not use the React toolchain (Prettier + linc + Flow), or when you only want to run one isolated test.

Security analysis

Caution
Quality score82/100

The skill does not contain destructive, exfiltrating, or obfuscated instructions; its commands are standard formatting, linting, type-checking, and testing steps. However, it does invoke shell/package scripts and subagents while declaring no allowed-tools, so it carries execution risk typical of build/test automation and should be treated as caution rather than fully safe.

Findings
  • •No allowed-tools are declared, but the skill instructs execution of shell commands (`yarn prettier`, `yarn linc`) and subagent slash commands (`/flow`, `/test`).
  • •`yarn` commands execute repository-defined package scripts, so the actual effect depends on the target repo's configuration.
  • •The skill delegates work to `/flow` and `/test` subagents without defining their behavior or permissions.
How this analysis is made

Examples

Pre-commit check
Vérifie mes changements avant que je commit, le motif de test est MyComponent
Full contribution requirements
Run the full verification: prettier, linc, flow type check, and tests for source and www
Validate a component change
Avant d'ouvrir la PR, lance la suite de vérification sur mon changement de composant React

name: verify description: Use when you want to validate changes before committing, or when you need to check all React contribution requirements.

Verification

Run all verification steps.

Arguments:

  • $ARGUMENTS: Test pattern for the test step

Instructions

Run these first in sequence:

  1. Run yarn prettier - format code (stop if fails)
  2. Run yarn linc - lint changed files (stop if fails)

Then run these with subagents in parallel:

  1. Use /flow to type check (stop if fails)
  2. Use /test to test changes in source (stop if fails)
  3. Use /test www to test changes in www (stop if fails)

If all pass, show success summary. On failure, stop immediately and report the issue with suggested fixes.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/verification-mrwakchq/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/verification-mrwakchq' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/verification-mrwakchq/download' --output '.skill-downloads/verification-mrwakchq/SKILL.md.part' && mv '.skill-downloads/verification-mrwakchq/SKILL.md.part' '.skill-downloads/verification-mrwakchq/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/verification-mrwakchq/SKILL.md' && test -s '.skill-downloads/verification-mrwakchq/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/verify' && cp -R '.skill-downloads/verification-mrwakchq' '.claude/skills/verify'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/verification-mrwakchq'

openskills read 'verification-mrwakchq'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/verification-mrwakchq/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills