# Verify > Run all verification checks (static analysis, test, format). Use this skill whenever the user asks to verify code quality, run all checks, or ensure the codebase is in a clean state before committing or deploying. Orchestrates static-analysis, test, and format skills in sequence. Use when this capability is needed. - Skill: `tomevault-io/verify-7` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/verify-7` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/verify-7/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/verify-7 --- # Verify Run all verification checks to ensure code quality. ## Workflow ### 1. Discover Project Commands and Runtime Before running any checks, identify available CLI commands and the execution environment: - Investigate available commands by checking project files such as `flake.nix`, `package.json` (scripts), `Makefile`, `justfile`, `README.md`, and any other relevant configuration - Also consider language-native commands (e.g., `go test`, `cargo test`, `cargo clippy`, `pytest`) based on the detected project type - Detect the runtime environment from lock files and configuration (e.g., `flake.lock`, `package-lock.json`, `go.sum`, `Cargo.lock`) - If a command fails on first execution, recommend the appropriate setup (e.g., `nix develop`, `npm install`, `go mod download`) ### 2. Run Checks Run in this order: 1. `static-analysis` skill (linting and type checking) 2. `test` skill (run the test suite) 3. `format` skill (run code formatters) ### 3. Fix Issues Fix any issues before proceeding to the next step. Do not go back to completed steps. --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/xantibody) — claim your Tome and manage your conversions.