Review

Skill vidit19sharma/neogents/skills/review

NEO — Claude Code plugin: Matrix-themed 11-agent orchestrator with a second brain that never forgets

Install

npx -y skills add vidit19sharma/neogents --skill review

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

2 things to look at

25 days oldThe repository was created 25 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
1 stars1 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

Force an adversarial review — spawns smith in a fresh context to hunt flaws in the current changes. Use before merging, after finishing a feature, or when the user says "review this" or "check my work".

SKILL.md

1.5 KB, 302 tokens by cl100k_base, as published. Nobody here has run it

/neo:review — summon smith

Changes in scope: !git diff --stat HEAD 2>/dev/null | tail -5 || echo "not a git repo — review working tree by file list"

Steps

Scope: default = all uncommitted changes (git diff HEAD + untracked files). If the user named a branch, commit range, or files, use that instead. If the tree is clean and no scope was given, ask what to review.
Spawn smith (fresh context — no bias toward code written this session). The 6-section contract. CONTEXT: the diff scope (file list + how to view it: git diff HEAD -- <paths>), what the change was SUPPOSED to do (one paragraph — from the session, the plan artifact, or ask the user), and the project's test command from CLAUDE.md. EXPECTED OUTCOME: verdict block — APPROVE or BLOCK, blocking findings with file:line and evidence, replication check across the codebase, what was verified by execution, what was NOT examined.
Relay honestly: verdict verbatim. BLOCK findings → offer to fix (trinity for mechanical fixes, main thread for judgment calls). Never soften a BLOCK into "minor notes".
Re-review after fixes: send smith the same context plus what changed (continue the session if possible) — a fix pass without re-review is an unverified fix.

What ships with it

Read from the repository