skills.rest
so-ota-biz
so-ota-bizCOMMUNITY
Explore all skills by this author →
GitHub

local-review

Identify diffs between local and remote default branches for parallel review reports.

Updated Aug 27, 2026
Search Tags:#code-review#report-generation#parallel-review#branch-diff#local-review#meta-check
One-click install
npx skills add https://github.com/so-ota-biz/ai-agent-orchestration-settings --skill local-review-so-ota-biz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: local-review
Source: https://github.com/so-ota-biz/ai-agent-orchestration-settings/tree/main/.agent/skills/local_review
Command: npx skills add https://github.com/so-ota-biz/ai-agent-orchestration-settings --skill local-review-so-ota-biz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill reviews the difference between the current local branch and the remote default branch, enabling focused code reviews and early quality gates.

Core Features & Use Cases

  • Parallel 4-agent harness (code-reviewer / code-quality-reviewer / must-check-reviewer + review-meta-checker) to provide independent review perspectives and protect against viewpoint contamination.
  • Generates three reports (review-report.md, quality-report.md, must-check-report.md) and saves intermediate artifacts to enable audits and replays.
  • Use cases include pre-PR reviews for feature branches, design-conformity checks against design documents, and cross-checking against project-wide guidelines.

Quick Start

Run the local-review skill on your current checkout to generate three parallel review reports and a final meta-check summary.

Frequently Asked Questions about local-review

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

FAQPage Schema
How do I run a pre-PR code review on my local feature branch?▼

A pre-PR code review is performed by identifying the diff between your local branch and the remote default branch, then running three independent parallel reviewers to generate separate reports and a final meta-check summary.

What is parallel code review and how does it prevent viewpoint contamination?▼

Parallel code review uses a 4-agent harness where independent reviewers run simultaneously to prevent viewpoint contamination, generating separate reports for code review, quality checks, and must-check validations.

Can I check design-conformity against project guidelines for local branch diffs?▼

Yes, you can check design-conformity by targeting the diff between your current local branch and the remote default branch, validating feature-branch adherence to design documents and project-wide guidelines.

What reports are generated from a local branch diff review?▼

A local branch diff review generates three separate markdown files: review-report.md, quality-report.md, and must-check-report.md, while saving intermediate artifacts to enable audits and replays alongside a final meta-check pass.

Does local branch review require any external dependencies or components?▼

No, local branch review requires no external dependencies or components to run. It enforces deterministic steps, context resolution, and artifact generation entirely within its own parallel review harness.

Related Skills

Explore More Software Engineering Skills→
fhrbatafhrbata

review-git-branch

Review local git branch commits and diffs since the fork point.

Community
Intermediate
xloxn69xloxn69
7

pr-description

Generate structured Markdown pull request descriptions for GitHub and GitLab.

Community
Basic
raybargasraybargas

Global Commenting

Enforces uniform, standard-based commenting across entire codebases and integrates with linters and static analysis tools for automated checks.

Community
Basic
YH-05YH-05
1

issue-implementation-serial

Implement multiple GitHub Issues sequentially into a single Pull Request.

Community
Advanced