code-review-small

Review small PR diffs for style, naming, and obvious bugs.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/rachel353/fullty-plan --skill code-review-small-rachel353
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-small
Source: https://github.com/rachel353/fullty-plan/tree/main/.claude/skills/code-review-small
Command: npx skills add https://github.com/rachel353/fullty-plan --skill code-review-small-rachel353

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Small PRs often get overlooked in longer reviews. This Skill provides a lightweight, fast review focusing on core quality signals to quickly surface issues.

Core Features & Use Cases

  • Code style and formatting
  • Naming conventions
  • Obvious bugs and typos
  • Basic logic errors
  • Output: a brief review summary highlighting issues found and suggested fixes

Quick Start

Review the attached PR diff and return a concise summary of issues found with suggested fixes.

Frequently Asked Questions about code-review-small

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

FAQPage Schema
How do I automate code review for small pull requests?

Automate code review for small pull requests by applying a focused review process that identifies code style issues, naming convention violations, and obvious bugs to output a concise summary of suggested fixes.

What is the best way to check code style and naming conventions in a PR diff?

Checking code style and naming conventions in a PR diff involves scanning the changes against standard formatting rules and naming patterns to quickly surface inconsistencies and maintain code quality.

Can I detect obvious bugs and basic logic errors in PRs under 100 lines?

Detecting obvious bugs and basic logic errors in PRs under 100 lines is achievable through deterministic review automation that targets typos and logic flaws to provide fast, focused feedback.

Does automated PR review work for large software changes?

Automated PR review for large software changes is not the focus here; this lightweight review targets small PRs with 100 lines or fewer to provide fast, deterministic quality checks.

How do I get a concise summary of issues found in a pull request?

To get a concise summary of issues found in a pull request, review the attached PR diff and generate a brief output highlighting detected style, naming, and logic problems with suggested fixes.

Why do small PRs often get overlooked in standard code review?

Small PRs often get overlooked in standard code review because longer reviews focus on broader changes, necessitating a lightweight, fast review to surface core quality signals in small diffs.