Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
vet
Run vet immediately after ANY logical unit of code changes. Do not batch your changes, do not wait to be asked to run vet, make sure you are proactive.
skill openclawclawhub Free
Run vet immediately after ANY logical unit of code changes. Do not batch your changes, do not wait to be asked to run vet, make sure you are proactive.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, scripts/export_codex_session.py, scripts/export_claude_code_session.py, scripts/export_opencode_session.py
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.2.4
Provenance
- Publisher
- andrewlaack-collab
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
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, pipx, or uv: # Using pip pip install verify-everything # Using pipx pipx install verify-everything # Using uv uv tool install verify-everything # Verify installation: vet --help
Standard Usage
Before running vet, determine the correct Python binary: $(command -v python3 || command -v python) Use whichever resolves (prefer python3). The examples below use python3, substitute python if that is what your system provides. OpenCode: vet "goal" --history-loader "python3 ~/.agents/skills/vet/scripts/export_opencode_session.py --session-id <ses_ID>" Codex: vet "goal" --history-loader "python3 ~/.codex/skills/vet/scripts/export_codex_session.py --session-file <path-to-session.jsonl>" Claude Code: vet "goal" --history-loader "python3 ~/.claude/skills/vet/scripts/export_claude_code_session.py --session-file <path-to-session.jsonl>" Without Conversation History vet "goal"
Finding Your Session
You should only search for sessions from your coding harness. If a user requests you use a different harness, they are likely referring to vet's agentic mode, not the session. OpenCode: The --session-id argument requires a ses_... session ID. To find the current session ID: Run: opencode session list --format json to list recent sessions with their IDs and titles. Identify the current session from the list by matching the title or timestamp. IMPORTANT: Verify the session you found matches the current conversation. If the title is ambiguous, compare timestamps or check multiple candidates. Pass the session ID as --session-id. Codex: Session files are stored in ~/.codex/sessions/YYYY/MM/DD/. To find the correct session file: Find the most unique sentence / question / string in the current conversation. Search for your unique message string in ~/.codex/sessions/` to find the matching session file. IMPORTANT: Verify the conversation you found matches the current conversation and that it is not another conversation with the same search string. Pass the matched file path as --session-file. Claude Code: Session files are stored in ~/.claude/projects/<encoded-path>/. The encoded path replaces / with - (e.g. /home/user/myproject becomes -home-user-myproject). To find the correct session file: Find the most unique sentence / question / string in the current conversation. Search for your unique message string in ~/.claude/projects/` to find the matching session file. IMPORTANT: Verify the conversation you found matches the current conversation and that it is not another conversation with the same search string. Pass the matched file path as --session-file. NOTE: The examples in the standard usage section assume the user installed the vet skill at the user level, not the project level. Prior to trying to run vet, check if it was installed at the project level which should take precedence over the user level. If it is installed at the project level, ensure the history-loader option points to the correct location.
Interpreting Results
Vet analyzes the full git diff from the base commit. This may include changes from other agents or sessions working in the same repository. If vet reports issues that relate to changes you did not make in this session, disregard them, assuming they belong to another agent or the user.
Common Options
--base-commit REF: Git ref for diff base (default: HEAD) --model MODEL: LLM to use (default: claude-opus-4-6) --list-models: list all models that are supported by vet Run vet --help and look at the vet repo's readme for details about defining custom OpenAI-compatible models. --confidence-threshold N: Minimum confidence 0.0-1.0 (default: 0.8) --output-format FORMAT: Output as text, json, or github --quiet: Suppress status messages and 'No issues found.' --agentic: Mode that routes analysis through the locally installed Claude Code or Codex CLI instead of calling the API directly. Try this if vet fails due to missing API keys. This is slower so it is not the default, but it often results in higher precision issue identification. --model is forwarded to the harness but not validated by vet, as vet doesn't know which models each harness supports. --agent-harness: The two options for this are codex and claude. Claude Code is the default. --help: Show comprehensive list of options
Updating
The vet CLI, skill files, and export scripts can become outdated as agent harnesses and LLM APIs change. If this happens, try updating them. Run which vet to determine how vet was installed and update accordingly. For the skill files, check which skill directories exist on disk and update them with the latest versions from https://github.com/imbue-ai/vet/tree/main/skills/vet.
Additional Information
Additional information can be found in the vet repo: https://github.com/imbue-ai/vet
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Scripts1 Docs
- SKILL.md
- scripts/export_claude_code_session.py
- scripts/export_codex_session.py
- scripts/export_opencode_session.py