vetlisted

# Vet **Run vet immediately after ANY logical unit of code changes. Do not batch changes, do not wait to be asked to run vet, make sure you are proactive.** Vet reviews git diffs and conversation history to find issues in code changes and conversation history. It is most effective when run frequently with conversation history, which helps it catch misunderstandings between what was requested and what was implemented. Despite this, vet is not a replacement for running tests. ## Installation Install vet using pip or uv: ```bash # Using pip pip install verify-everything # Using uv (recommended) uv pip install verify-everything # Verify installation: vet --help ``` ## Running Vet ### Standard Usage **OpenCode:** ```bash vet "goal" --history-loader "python ~/.agents/skills/vet/scripts/export_opencode_session.py --session-id <ses_ID>" ``` **Codex:** ```bash vet "goal" --history-loader "python ~/.codex/skills/vet/scripts/export_codex_session.py --session-file <path-to-session.jsonl>" ``` **Claude Code:** ```bash vet "goal" --history-loader "python ~/.claude/skills/vet/scripts/export_claude_code_session.py --session-file <path-to-session.jsonl>" ``` **Without Conversation History** ```bash vet "goal" ``` ### Finding Your Session **OpenCode:** The `--session-id` argument requires a `ses_...` session ID. To find the current session ID, search for the first user message from this conversation in the part files: 1. Find the most unique sentence / question / string in the c