verify-all
Skill9 starsChanged 20 days agoMITView on GitHub
Run every local quality check (lint and format, types, tests, accessibility, design tokens, dead code, security, bundle size, agent plugins, renderers, Claude Code conformance) through ./scripts/verify-all.sh and report a pass/fail summary. Use before opening a pull request or calling work done. Keywords: verify all, quality gate, run all checks
In this repository32 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- animation-motionSkill
- auth-flowsSkill
- build-from-canvaSkill
- build-from-conversationSkill
- build-from-figmaSkill
- build-from-screenshotSkill
- canva-intakeSkill
- canva-token-inferenceSkill
- ciSkill
- conversation-intakeSkill
- design-brief-to-figmaSkill
- design-token-lockSkill
- e2e-test-generatorSkill
- export-design-systemSkill
- figma-intakeSkill
- figma-to-react-workflowSkill
- form-handlingSkill
- indesign-conversionSkill
- lintSkill
- parallel-orchestrationSkill
- react-accessibilitySkill
- react-component-developmentSkill
- react-performance-optimizationSkill
- react-testing-workflowsSkill
- screenshot-intakeSkill
- seo-metadataSkill
- state-managementSkill
- storybook-story-generationSkill
- tdd-from-figmaSkill
- testSkill
- visual-qa-verificationSkill
The file
Files
/verify-all — Run All Local Quality Checks
Runs every local quality check in sequence and reports a pass/fail summary. Wraps ./scripts/verify-all.sh so you do not have to remember each individual script.
Usage
/verify-all
/verify-all --skip dead-code,security
/verify-all --include lint-and-format,types,testsOptional flags forward to the underlying script:
--skip <a,b,c>— skip named checks (comma-separated)--include <a,b>— run only the named checks--list— list available check names and exit
For machine-readable output and CI-style behavior, use /ci instead.
What runs
The orchestrator runs these checks in order. Each is independent — a failure in one does not stop the others.
| # | Check | Backing script | What it does |
| 1 | lint-and-format | lint-and-format.sh --check | ESLint + Prettier (no auto-fix) |
| 2 | types | check-types.sh | tsc --noEmit |
| 3 | tests | run-tests.sh | Vitest with coverage |
| 4 | accessibility | check-accessibility.sh | ESLint with jsx-a11y rules |
| 5 | tokens | verify-tokens.sh | Hardcoded-value scan vs lockfile |
| 6 | dead-code | check-dead-code.sh | Knip: unused exports/files/deps |
| 7 | security | check-security.sh | Dependency audit + anti-pattern scan |
| 8 | bundle-size | check-bundle-size.sh | Bundle analysis (skipped if no build artifact) |
| 9 | agent-plugins | verify-agent-plugins.sh | Validates and tests agent plugins (skipped when .claude/agent-plugins/ is empty) |
| 10 | renderers | verify-renderers.sh | Validates every renderer manifest |
| 11 | claude-code | claude-code-conformance.js | .claude/ agents, skills, hooks and plugin manifest against the current Claude Code spec |
Steps
1. Run the orchestrator
./scripts/verify-all.sh $ARGUMENTSThe script prints per-check progress and a summary table at the end:
=== Summary ===
Check Status Duration Reason
----- ------ -------- ------
lint-and-format pass 2618ms
types pass 1843ms
tests pass 4205ms
accessibility pass 1102ms
tokens pass 320ms
dead-code pass 2980ms
security pass 4111ms
bundle-size skip 0ms no build artifact (dist/.next/build/out)
agent-plugins skip 0ms no plugins under .claude/agent-plugins
renderers pass 410ms
claude-code pass 180ms
Totals: 9 passed, 0 failed, 2 skipped
✓ All checks passed.2. If any check fails
The summary lists the exact command to reproduce each failure with full output. Re-run that one script to see the underlying errors:
./scripts/lint-and-format.sh --checkOnce the failing check is fixed, re-run /verify-all to confirm.
Exit codes
0— every check passed (or was skipped intentionally)1— one or more checks failed
Related
/ci— same checks, JSON output, non-interactive (for automation / CI)/lint— lint and format only/test— tests only
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

