review

Unify local branch and GitHub PR reviews into a single workflow.

31|5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/NSEvteev/FullSpec --skill review-nsevteev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/NSEvteev/FullSpec/tree/main/.claude/skills/review
Command: npx skills add https://github.com/NSEvteev/FullSpec --skill review-nsevteev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review is often split between local branch review and GitHub PR review. This skill unifies both steps into a single, cohesive workflow to streamline validation and feedback before pushing or merging.

Core Features & Use Cases

  • Unified review flow for local branches and PRs, ensuring consistent feedback and validation across the development cycle.
  • Orchestrates per-service review steps and produces an aggregated verdict to guide merge decisions.
  • Integrates with repository documentation to maintain traceability and governance.

Quick Start

Review the current branch or open PR using the unified code-review workflow before pushing or merging.

Frequently Asked Questions about review

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

FAQPage Schema
How do I run a local code review for a Git branch before pushing?

A unified code review combines branch and PR validation into a single workflow before merging. It coordinates parallel code-reviewer agents per service, applies validation prerequisites, and produces an aggregated verdict to ensure consistent feedback across the development cycle.

Can I use this to review pull requests across multiple services simultaneously?

Yes, this unified code review workflow supports pull requests by running parallel code-reviewer agents per service. It coordinates per-service validation blocks and aggregates their results into a final verdict, ensuring comprehensive multi-service PR coverage.

What's the best way to automate quality assurance checks for code merges?

Automate quality assurance by applying the unified code review workflow before merging. It enforces standard-review prerequisites, runs per-service validation blocks, and generates an aggregated verdict to ensure merge readiness across branches and PRs.

Do I need specific validation files to start the code review workflow?

Yes, the code review workflow follows validation-review.md and standard-review.md prerequisites. These repository documentation files must exist to maintain traceability, establish governance, and provide the validation steps required before the review status updates.

Why does my branch validation produce a blocked status during code review?

A blocked status occurs when per-service validation steps fail during the unified code review. The workflow coordinates these per-service blocks individually before pushing or merging, and any failed block prevents the final aggregated verdict from passing.