verify

In Codex, first read the native runtime adapter.

Verify (/fakoli-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 /fakoli-flow:execute completes
• Manually when the user runs /fakoli-flow:verify
• By /fakoli-flow:quick after the agent finishes

---

Step 1: Detect Project Language

Run the following to determine which verification commands apply:

# 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:

npx tsc --noEmit && bun test

Python:

ruff check . && mypy . && pytest

Rust:

cargo check && cargo test

Capture the full output of each command. Read exit codes. Count errors explicitly — do not skim.

---

Step 3: Dispatch Sentinel (if fakoli-crew is available)

If fakoli-crew is installed, dispatch the sentinel agent with the acceptance criteria from the plan.

How to find the plan:

ls docs/plans/ | sort | tail -1

Read the most recent plan file. Extract the acceptance criteria for each task (the **Acceptance criteria:** bullet points under each task heading).