Overview

Code Review Small provides a lightweight review for small PRs under 100 lines changed. It targets basic code quality, naming conventions, and obvious bugs or typos, helping maintainers catch issues quickly.

How This Skill Works

A quick pass over the changed files checks code style and formatting, naming conventions, and signals obvious bugs and basic logic errors. It then outputs a brief review summary with any issues found.

When to Use It

• Review a patch under 100 lines before merging
• When a fast QA pass is needed for minor changes
• To catch obvious typos and naming inconsistencies early
• During lightweight code hygiene checks in sprints
• Before a deeper or full review when time is limited

Quick Start

1. Step 1: Load the PR diffs and run the lightweight code-review pass
2. Step 2: Flag issues in style, naming, typos, and basic logic in changed files
3. Step 3: Deliver a brief summary of findings with suggested fixes

Best Practices

• Limit the scope to the changed files and verify only the touched logic
• Prioritize naming consistency and readability in new/updated identifiers
• Spot obvious bugs, typos, and off-by-one or conditional errors in touched areas
• Ensure code style and formatting align with project standards
• Provide a concise summary of issues with concrete, actionable fixes

Example Use Cases

• PR fixes a broken error message with a typo; reviewer notes the corrected wording and impact
• Small refactor introduces inconsistent naming; reviewer recommends aligning function names and param names
• Minor bug fix reveals a missing edge-case check; reviewer suggests adding a guard for null input
• Added small helper function with unclear name; reviewer suggests renaming for clarity
• Patch under 100 lines fixes a boundary condition bug in a loop and updates tests accordingly

Frequently Asked Questions