review

Review git diffs for correctness, style, and Rust conventions.

1|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/89jobrien/dotfiles --skill review-89jobrien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/89jobrien/dotfiles/tree/main/dot-claude/skills/review
Command: npx skills add https://github.com/89jobrien/dotfiles --skill review-89jobrien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review staged changes for correctness, style, and Rust conventions before committing.

Core Features & Use Cases

  • Check correctness of changed code and identify off-by-one or logic errors
  • Enforce Rust conventions and SOLID design principles
  • Produce a concise, actionable verdict with issues and suggestions

Quick Start

Run the review on the current diff before committing to catch issues early.

Frequently Asked Questions about review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review Rust code diffs for correctness and convention issues before committing?

To review Rust code diffs before committing, run a review process against your staged or unstaged git changes to identify logic errors, improper error handling, and Rust convention violations. This produces a concise issues report with actionable suggestions and a final verdict.

What is the best way to catch security concerns and logic errors in a Rust git diff?

The best way to catch security concerns in a Rust git diff is to analyze the staged changes for proper error handling and test coverage before committing. This process checks code quality and correctness, delivering a report with identified issues and improvement suggestions.

Can I check unstaged git changes for Rust style and SOLID design principles?

Yes, you can check both staged and unstaged git changes for Rust style and SOLID design principles. The review process evaluates the diff output to enforce conventions and design correctness, resulting in an actionable verdict with specific issues and suggestions.

Does reviewing Rust diffs for test coverage require the Rust toolchain?

Yes, reviewing Rust diffs for test coverage and correctness requires access to git diff outputs and the Rust toolchain. Evaluating staged or unstaged changes with these tools produces a concise issues report with suggestions and a final commit verdict.

When should I review a git diff for code quality before a commit?

You should review a git diff for code quality immediately before committing to catch off-by-one errors, security concerns, and convention issues early. Running this check on staged or unstaged Rust changes yields a concise report with suggestions and a final verdict.