verifylisted

# Verify (`/flow:verify`) ## Overview Verification is not an opinion. It is a command you ran, output you read, and a result you can cite. **Core principle:** Every PASS must cite fresh command output from this session. Every FAIL must cite what the output actually showed. **This skill is invoked:** - Automatically after `/flow:execute` completes - Manually when the user runs `/flow:verify` - By `/flow:quick` after the agent finishes --- ## Step 1: Detect Project Language Run the following to determine which verification commands apply: ```bash # Check for language markers in order of specificity [ -f tsconfig.json ] && echo "TypeScript" [ -f Cargo.toml ] && echo "Rust" { [ -f pyproject.toml ] || [ -f setup.py ]; } && echo "Python" ``` | Marker file | Language | |-------------|----------| | `tsconfig.json` or `package.json` | TypeScript | | `Cargo.toml` | Rust | | `pyproject.toml` or `setup.py` | Python | If multiple markers exist, prefer the most specific: `tsconfig.json` > `package.json`. If no marker is found: ask the user before proceeding. --- ## Step 2: Run Language-Appropriate Checks Run the full command for the detected language. Do not split it. Do not skip a step because the previous one passed. **TypeScript:** ```bash npx tsc --noEmit && bun test ``` **Python:** ```bash ruff check . && mypy . && pytest ``` **Rust:** ```bash cargo check && cargo test ``` Capture the full output of each command. Read exit codes. Count errors explicitly — do not skim