skills.rest
Lev-it
Lev-itOFFICIAL
Explore all skills by this author →
GitHub

review

Review Git code changes for coding standards and specification compliance.

Updated Apr 28, 2026
Search Tags:#code review#version control#parallel processing#coding standards#specification compliance
One-click install
npx skills add https://github.com/Lev-it/lev-skills --skill review-lev-it
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Lev-it/lev-skills/tree/main/.claude/skills/review
Command: npx skills add https://github.com/Lev-it/lev-skills --skill review-lev-it

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a streamlined approach to code review, enabling users to evaluate changes against coding standards and specifications efficiently.

Core Features & Use Cases

  • Two-axis Review: Concurrently analyzes code changes for adherence to coding standards and specification compliance.
  • Parallel Sub-agents: Ensures each axis of review is isolated from the other, maintaining purity of results.
  • Integration with Issue Tracker: Facilitates the use of issue trackers for identifying and referencing originating specifications.

Quick Start

To initiate a review, use the command: /review since <commit_hash> or /review since <branch_name>

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review against coding standards and specifications?▼

Automated code review evaluates Git changes concurrently for coding standards and specification compliance. It uses parallel sub-agents to isolate each review axis, ensuring pure results without cross-contamination between checks.

How do I run a code review since a specific commit or branch?▼

Run a code review since a specific commit by using the command syntax /review since <commit_hash> or /review since <branch_name>. This triggers the two-axis evaluation against documented standards and originating specifications.

Do I need an issue tracker configured to review specification compliance?▼

Yes, a properly configured issue tracker is required to review specification compliance. The issue tracker is used for identifying and referencing the originating specifications needed for the evaluation.

Can I use this for version control systems other than Git?▼

No, this code review process supports Git-based version control systems exclusively. It evaluates changes by analyzing Git commits and branches against your documented standards and project specifications.

How does parallel processing improve code review results?▼

Parallel processing improves code review by utilizing isolated sub-agents for each review axis. This prevents contamination between the coding standards check and the specification compliance check, maintaining the purity of the evaluation results.

Related Skills

Explore More Software Engineering Skills→
guille-galloguille-gallo

review

Review code changes against coding standards and specifications.

Community
Advanced
druejaramillodruejaramillo

code-review

Compare git revision ranges and generate standards and specification reports.

Community
Advanced
tsuji-tomonoritsuji-tomonori

a11y-ci-gating

Automate accessibility testing in CI/CD pipelines with quality gates.

Community
Advanced
AtharvaN16AtharvaN16

code-review

Review code changes against coding standards and specifications using parallel sub-agents.

Community
Advanced