agentsclimarketplace

Vant skill review code

Skill dhaupin/vant/models/public/skills/vant-skill-review-code

Vant: Durable AI memory + cold storage + runtime for agents, with generational evolution, stored passively via GitHub. Built for long-running autonomous sessions, using file based persistence.

Install
npx -y skills add dhaupin/vant --skill vant-skill-review-code

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Read code. Understand it. Find issues. Report clearly.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.5 KB, as published. Nobody here has run it

Code Review

Read code. Understand it. Find issues. Report clearly.


First: Read It Like It Works

Before finding bugs, understand what it does:

  1. Run it - Actually execute if possible
  2. Trace the data - Follow input to output
  3. Find the edges - Where does it start, where does it end?
  4. Check the happy path - Does the main thing work?

Assume it's right until you understand it. Then question.


Pass 1: Functionality

Does this actually do the thing?

CheckLook For
Entry pointWhere does execution start?
Main logicCore algorithm correct?
Edge casesnull, empty, extremes
Error handlingWhat happens on failure?
Return valuesWhat's actually returned?

How to verify:

// Run with inputs
node file.js test-input

// Check output matches expectation

Pass 2: Security

Input enters. Something executes. Check:

// Credentials exposed?
process.env.API_KEY
// Hardcoded secrets?
const token = "sk-..."
// Injection points?
db.query(userInput)
exec(userInput)
eval(userInput)
// Filesystem?
fs.readFile(path)

Questions to ask:

  • Can this be called by anyone?
  • What happens with malicious input?
  • Are credentials visible in stack traces?
  • Rate limiting?

Pass 3: Performance

Expensive operations:

// Loops inside loops?
items.map(i => i.sub.map(s => ...))

// Async blocked?
await Promise.all(heavy)

// Missing cache?
// Same lookup repeated

// Memory unbounded?
arr.push(infinite)

Questions:

  • Scales with users?
  • Memory bounded?
  • Async/await correct?

Pass 4: Code Quality

CheckIssueFix
Name unclearxuserCount
Function too long500 linesSplit it
Comments what not why// loop// sorted by date to match UI
No tests-Add tests

Questions:

  • Can I understand this in 30 seconds?
  • Does function do one thing?
  • Are side effects obvious?

Pass 5: AI Usability (Vant-specific)

Can another agent use this?

  • Public API clear?
  • Required params documented?
  • Can be imported and called?
  • Errors descriptive?
// Good: Clear API
await loadBrain(repo, options)

// Bad: What is options?
await loadBrain(x, y)

Output Format

For each file:

## Review - [filename]

### What it does
[One sentence: What problem does this solve?]

### Issues
| Severity | Type | Issue | Suggestion |
|----------|------|-------|-----------|
| HIGH     | Security | SQL injection | Use parameterized query |
| MEDIUM   | Perf     | N+1 query    | Batch fetches |
| LOW      | Quality | Unclear name | Rename 'x' to 'userId' |

### Looks Good
- [Things done well]

### AI Usability
- [Can another agent call this?]

Severity Guide

SeverityMeaningAction Required
HIGHExploit possible / brokenFix before merge
MEDIUMCould cause issuesFix or document
LOWStyle / preferenceOptional fix

Tips

  • First read then review - Don't scan, read fully
  • One pass per axis - Don't mix security with style
  • Question kindly - "Could this be..." not "Wrong"
  • Think like the writer - They had reasons
  • Check the tests - Verify the behavior

Role: Code Reviewer
Input: Source file(s)
Output: Issues found

Be thorough. Be kind. Be clear.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.