skills.rest
looooonk
looooonkCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-review-change-size

Enforces change size limits and suggests staging for large code review diffs.

5|1|Updated Jun 26, 2026
Search Tags:#code review#pull request#staging#review guidelines#change size#diff size
One-click install
npx skills add https://github.com/looooonk/better-codex --skill code-review-change-size-looooonk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-change-size
Source: https://github.com/looooonk/better-codex/tree/main/.codex/skills/code-review-change-size
Command: npx skills add https://github.com/looooonk/better-codex --skill code-review-change-size-looooonk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Oversized pull requests are hard to review thoroughly, leading to missed defects and slow review cycles. This Skill enforces line-count limits on code changes and guides reviewers on splitting large diffs into reviewable stages. ## Core Features & Use Cases - Change Size Enforcement: Caps non-mechanical changes at 800 lines and complex logic changes at 500 lines. - Staging Guidance: For oversized diffs, analyzes the actual diff, dependencies, and affected call sites to propose the smallest coherent stage to land first. - Use Case: A developer submits a 1,500-line refactor touching multiple modules. The Skill flags the size violation and recommends splitting it into sequential reviewable stages based on dependency order. ## Quick Start Review this pull request and check whether the change size stays within the line limits, suggesting how to split it if it is too large.

Frequently Asked Questions about code-review-change-size

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

FAQPage Schema
How do I check if a pull request is too large to review?▼

Count the total changed lines in the diff. Non-mechanical changes should stay under 800 lines, and complex logic changes under 500 lines. Anything larger should be evaluated for splitting into reviewable stages.

How to split a large code change into smaller reviews?▼

Analyze the diff's dependencies and affected call sites to find coherent boundaries. Identify the smallest self-contained stage that can land first, then sequence the remaining changes as follow-up stages.

What is the maximum recommended pull request size?▼

This guidance sets 800 lines as the maximum for general changes and 500 lines for complex logic changes. Mechanical changes such as generated code or renames are exempt from the strict limit.

When is a large diff acceptable without splitting?▼

Mechanical changes, such as automated refactors, generated code, or bulk renames, may exceed the line limits because they require minimal per-line scrutiny. Complex logic changes should still stay under 500 lines.

Related Skills

Explore More Software Engineering Skills→
NextSpark-jsNextSpark-js

impact-analysis

Analyze Git diffs to classify modified files and identify affected system flows.

Official
Intermediate
andreasasprouandreasasprou

rewrite-pipeline

Automate sequential implementation of rewrite plans into branches and pull requests.

Community
Advanced
richardnpaulrichardnpaul

django-verification

Verify Django projects for migrations, linting, tests, and security checks.

Community
Advanced
crbnoscrbnos
2.3k

pr-splitter

Split large pull requests into smaller reviewable pull requests using git.

Official
Advanced