review
Skill196 starsChanged 14 days agoMITView on GitHub
Multi-agent code review for Rust CLI/TUI. UX Review inactive (terminal UI — no web frontend). Code Review only. Includes Rust/clippy-specific checklist.
192 other projects use a version of this.
Adopted by
Most recently taken up by
- dzhng/skillstheir own version, first seen Nov 15, 2026
- muxy-app/muxytheir own version, first seen Nov 15, 2026
- macro-inc/macrotheir own version, first seen Nov 15, 2026
- igoroliveirg/claude-copytheir own version, first seen Nov 15, 2026
- yagizdo/quivertheir own version, first seen Nov 15, 2026
- markmhendrickson/neotomatheir own version, first seen Nov 15, 2026
Used with
Projects with it also use close-spec, daily-arxiv and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
dzhngSkillclose-spec
When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).
Also in 5 projects that use this
LambenthanSkilldaily-arxiv
每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新
Also in 5 projects that use this
dzhngSkilldesign-with-images
Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.
Also in 5 projects that use this
LambenthanSkillexp-eval
实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges
Also in 5 projects that use this
- +5 more from Lambenthan
- +3 more from dzhng
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- garrytan/gstack★ 142ksame name
- ansible/ansible★ 71ksame name
- docling-project/docling★ 71ksame name
- traefik/traefik★ 66ksame name
- ClickHouse/ClickHouse★ 51ksame name
- temporalio/temporal★ 24ksame name
- ccch1mneyyy/dsh-Go★ 24ksame name
- tisfeng/Easydict★ 15ksame name
- juicedata/juicefs★ 15ksame name
- elie222/inbox-zero★ 13ksame name
182 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 156 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Run Code Review Agent only.
- Distinctive: line 74
If there are clippy warnings, FAIL before starting review (should have been caught by verify).
- Distinctive: line 86
Do not run UX Review Agent (TUI project)
“Common” is measured: kept by at least 6 in 10 of the 156 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Review (toktrack override)
Follows the global /review multi-agent pattern, with the following overrides:
Override: UX Review Inactive
This project is a terminal TUI app — do not run the UX Review Agent. Run Code Review Agent only.
Override: Code Review Checklist Extension
In addition to the global checklist, append the following to the Code Review Agent prompt:
Critical (PLAN gate)
| Category | Items |
| PLAN assumption refutation | Does the diff falsify the [agent-inferred]/[unverified-gate] assumptions from the PLAN (falsified → P1+, carry to wrap) |
Author Review Gate (P0 — Identity / Matrix)
This repo is OSS and the reviewer is the author (receiving PRs). Generic code health is covered by Rust/TUI/clippy below; this section examines product-specific risks that only the author can validate. Perspective SSOT: session memory feedback_review_perspective.md.
| Tier | Category | Items |
| reject | Identity ① ultra-fast | Adding latency·blocking IO·synchronous network to hot path/startup → reject |
| reject | Identity ② persistent cache / data preservation | Risk of cache·history loss or corruption → reject. backward-compat·graceful degradation are the means to uphold this |
| ruthless | Irreversible | breaking change · data migration · public behavior change |
| ruthless | Environment/state matrix (contributors test only their own machine) | OS(paths·home·file locks·Windows) / source schema version(forward new-schema+backward old-format, new source·parser PRs require old-version·unknown-schema fixture) / data shape(empty·large·corrupt·partial·permissions) / locale·TZ·DST / concurrency(read race while source file is being written) / terminal(width·color·TERM) / first-run vs upgrade migration |
| bias to YES | Other features·ideas | Stars are the goal — acceptance bias. But if it taxes either core(weighing down hot path·startup·cache paths), request location·approach adjustment only. additive/opt-in/lazy/behind a flag = welcome |
| lenient | Style·naming preferences | Linter takes precedence, bikeshed prohibited (uniform strictness = contributor friction → star loss) |
| signal | Direction/growth fit (not a gate) | Beyond code quality·conventions, every contribution(issue·PR) also gets a direction-fit verdict in the review output: strengthens wedge (persistent cache/data preservation) / neutral (additive) / dilutes focus (e.g. feature-parity chasing) + 1–2 lines of rationale. Weigh holistically: maintenance cost vs value, real value to target users(AI CLI heavy users), contribution to project direction. Never a reject reason — the two identities above remain the only gates, bias-to-YES stands |
Rust-specific
| Category | Items |
| Safety | Minimize unsafe usage, comment with justification |
| Ownership | Unnecessary .clone(), to_string(), to_owned() |
| Error | anyhow/thiserror pattern consistency, no unwrap() (tests excluded) |
| Performance | Unnecessary allocation, Vec vs iterator chain, Box<dyn> vs generic |
| SIMD | Check fallback branch in simd-json parsing path |
| Concurrency | Check shared mutable state in rayon parallel path |
TUI-specific
| Category | Items |
| Widget | ratatui Widget trait implementation consistency |
| Theme | Use theme.rs semantic colors (no hardcoded colors) |
| Layout | Handle terminal resize (Rect boundary check) |
| Input | Missing keyboard event handling (shortcuts registered in help vs actual handlers) |
Clippy/Fmt Pre-check
Code Review Agent checks the following before review:
cargo fmt --check
cargo clippy --all-targets --all-features -- -D warningsIf there are clippy warnings, FAIL before starting review (should have been caught by verify).
Execution
- Collect context (diff, conventions, architecture, Sprint Contract)
- PLAN provenance tags/gates (if present) —
[agent-inferred]/[unverified-gate]
- PLAN provenance tags/gates (if present) —
- Launch Code Review Agent only (feature-dev:code-reviewer)
- Global
agents/code-review.mdprompt + above author gates + Rust/TUI checklist append
- Global
- Parse verdict → PASS → /wrap, FAIL → fix → /verify → re-review
Rules
- Sub-agent model: launch the Code Review Agent via the Agent tool with
model: "sonnet"(Sonnet 5). - Do not run UX Review Agent (TUI project)
- PASS → run /wrap immediately
- FAIL → fix → /verify → re-review (max 3)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

