review-local

Analyze local commits against origin/main for pre-PR quality issues.

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/acatl/some-skills --skill review-local-acatl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-local
Source: https://github.com/acatl/some-skills/tree/main/skills/review-local
Command: npx skills add https://github.com/acatl/some-skills --skill review-local-acatl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when the user wants a pre-PR self-review of local commits against origin/main. Adapts to the project's stack and conventions — reads CLAUDE.md, package manifests, and architecture docs to calibrate review lenses.

Not for: reviewing someone else's PR (use triage-pr-comments for that), running the full PR submission workflow (use start-pr-cycle), or reviewing a single file in isolation.

Core Features & Use Cases

  • Self-checks against origin/main to surface regressions and misalignments.
  • Phase-driven execution using a sub-agent to gather data and present actionable insights in the main conversation.
  • Adapts review lenses to project conventions, CLAUDE.md, and architecture docs; flags deviations and risks.

Quick Start

Run the review on your current branch to compare changes against origin/main.

Frequently Asked Questions about review-local

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

FAQPage Schema
How do I do a pre-PR self-review of local git commits against main?

Pre-PR self-review analyzes local git commits against origin/main to surface quality and conformity issues before submitting a pull request, adapting review lenses to your project stack and conventions.

Can I review a single file in isolation before creating a pull request?

No, this pre-PR review is not designed for reviewing a single file in isolation. It analyzes changes across CLAUDE.md, manifests, architecture docs, and project conventions across your local branch.

How does the code review process adapt to my project's architecture?

The code review adapts by reading CLAUDE.md, package manifests, and architecture docs to calibrate review lenses, automatically flagging deviations and risks based on your specific project stack.

What is the best way to review someone else's pull request comments?

To review someone else's PR, use a dedicated triage-pr-comments workflow instead of this local commit review tool, which is strictly built for self-reviewing your own local changes against main.

Does the pre-PR review provide actionable fixes for quality issues?

Yes, the pre-PR review enforces a disciplined workflow with structured findings, risk assessment, and actionable fixes, using a sub-agent to gather data and present insights directly in the main conversation.