vet
Review code with vet after every change
Vet helps AI coding assistants identify issues in their code changes by analyzing git diffs and conversation history. Run it immediately after any logical unit of code changes to catch misunderstandings between what was requested and what was implemented.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "vet". Run vet on the current changes
Expected outcome:
Vet found 2 issues:
1. [HIGH] Unused variable in auth.py:23
The variable 'token' is assigned but never used.
2. [MEDIUM] Missing error handling in database.py:45
Database connection errors are not caught.
Recommendation: Review these issues before committing.
Using "vet". Run vet with --output-format json
Expected outcome:
{"issues": [{"severity": "high", "file": "auth.py", "line": 23, "message": "Unused variable 'token'"}, {"severity": "medium", "file": "database.py", "line": 45, "message": "Missing error handling"}]}
Security Audit
SafeThis is a legitimate code review tool that analyzes AI assistant session history and git diffs. The static scanner flagged 54 potential issues, but all are false positives. The 'weak cryptographic algorithm' alerts are triggered by argparse (command-line parsing), not crypto code. 'Shell backtick' alerts are markdown code blocks showing example commands, not actual execution. 'Hidden file' and 'system reconnaissance' alerts are legitimate file path accesses to session storage required for the tool to function.
High Risk Issues (3)
Low Risk Issues (1)
Quality Score
What You Can Build
Catch bugs early in development
Run vet after each code change to catch bugs before they accumulate. The tool reviews the git diff and conversation context to identify potential issues.
Improve code quality during feature development
Use vet to verify implementation matches user intent by analyzing conversation history alongside code changes.
Review AI-generated code manually
Vet provides an additional layer of review for AI-generated code, catching issues that the AI may have missed.
Try These Prompts
Run vet on the current changes to review the code.
Run vet on the current changes focusing on security issues.
Run vet using the claude-sonnet-4 model with a 0.9 confidence threshold.
Run vet in agentic mode to route through local Claude Code CLI.
Best Practices
- Run vet immediately after every logical unit of code changes, not in batches
- Review issues that relate to changes you actually made, not other agents
- Use the --agentic mode when API keys are unavailable but expect slower analysis
Avoid
- Do not ignore issues without reviewing them - they may indicate real problems
- Do not run vet only at the end of a large feature - catch issues early
- Do not assume vet replaces testing - it complements but does not replace tests