Review (toktrack override)

SkillAI & models

Multi-agent code review for Rust CLI/TUI. UX Review inactive (terminal UI — no web frontend). Code Review only. Includes Rust/clippy-specific checklist.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Review (toktrack override) skill

What this skill tells your AI

The instructions your AI receives, as published by mag123c/toktrack in .claude/skills/review/SKILL.md and read by ahel’s review.

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)

CategoryItems
PLAN assumption refutationDoes 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.

TierCategoryItems
rejectIdentity ① ultra-fastAdding latency·blocking IO·synchronous network to hot path/startup → reject
rejectIdentity ② persistent cache / data preservationRisk of cache·history loss or corruption → reject. backward-compat·graceful degradation are the means to uphold this
ruthlessIrreversiblebreaking change · data migration · public behavior change
ruthlessEnvironment/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 YESOther features·ideasStars 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
lenientStyle·naming preferencesLinter takes precedence, bikeshed prohibited (uniform strictness = contributor friction → star loss)
signalDirection/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

CategoryItems
SafetyMinimize unsafe usage, comment with justification
OwnershipUnnecessary .clone(), to_string(), to_owned()
Erroranyhow/thiserror pattern consistency, no unwrap() (tests excluded)
PerformanceUnnecessary allocation, Vec vs iterator chain, Box<dyn> vs generic
SIMDCheck fallback branch in simd-json parsing path
ConcurrencyCheck shared mutable state in rayon parallel path

TUI-specific

CategoryItems
Widgetratatui Widget trait implementation consistency
ThemeUse theme.rs semantic colors (no hardcoded colors)
LayoutHandle terminal resize (Rect boundary check)
InputMissing 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 warnings

If there are clippy warnings, FAIL before starting review (should have been caught by verify).

Execution

  1. Collect context (diff, conventions, architecture, Sprint Contract)
    • PLAN provenance tags/gates (if present) — [agent-inferred] / [unverified-gate]
  2. Launch Code Review Agent only (feature-dev:code-reviewer)
    • Global agents/code-review.md prompt + above author gates + Rust/TUI checklist append
  3. 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)

Signals

GitHub stars
189
Forks
20
Last commit
Sep 2026
Hacker News mentions
20
Advanced
Catalog kind
skill
Gateway key
review-mag123c
Source
github.com/mag123c/toktrack