review

Inspects selected files or Git diff for compliance with project-specific rules and conventions.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/karimatayuta/graph-vector-rag --skill review-karimatayuta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/karimatayuta/graph-vector-rag/tree/main/.claude/skills/review
Command: npx skills add https://github.com/karimatayuta/graph-vector-rag --skill review-karimatayuta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review is often manual and inconsistent; this skill provides a structured, repeatable review focusing on correctness, style, and architecture.

Core Features & Use Cases

  • Scope-aware review: reviews by file, diff, branch, or uncommitted changes.
  • Conformance checks: enforces code style, architecture patterns, and testing conventions.
  • Quality guidance: provides actionable recommendations aligned with project conventions.

Quick Start

Provide a structured code review for the latest changes in the repository.

Frequently Asked Questions about review

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

FAQPage Schema
How do I perform a structured code review on recent changes or diffs?

A structured code review targets specific files, diffs, staged changes, branches, or uncommitted work. It evaluates correctness, style, and architecture against repository conventions to catch issues fast and provide actionable recommendations.

What architectural patterns does a code review checklist enforce for Python projects?

A code review checklist enforces type hints, the repository pattern, Pydantic models, lazy imports, and parameterized queries. It also checks for comprehensive testing to ensure conformance with project conventions.

Can I review uncommitted changes and staged files before pushing a branch?

You can review uncommitted changes and staged files before pushing. The review scope is flexible and can target specific files, diffs, or entire branches to ensure code quality prior to integration.

Why does my code review fail when missing type hints or Pydantic models?

A code review fails when missing type hints or Pydantic models because it requires strict adherence to repository conventions. These conformance checks ensure architectural consistency and validate data structures.

What is the best way to automate software engineering review checklists for diffs?

Automating review checklists for diffs uses a structured skill that applies conformance checks for style, architecture patterns, and testing conventions. This provides repeatable, actionable recommendations for recent changes.