code-review-change-size
$
npx mdskill add openai/codex/code-review-change-sizeAssess proposed code modifications to ensure they fit within recommended review size limits.
- Guides developers on keeping pull requests manageable for efficient peer review.
- Requires access to the code diff to calculate line counts and analyze structure.
- Analyzes the total lines changed and suggests splitting large modifications into stages.
- Outputs a recommendation detailing size compliance or proposing a staged rollout plan.
SKILL.md
.github/skills/code-review-change-sizeView on GitHub ↗
--- name: code-review-change-size description: Change size guidance (800 lines) --- Unless the change is mechanical the total number of changed lines should not exceed 800 lines. For complex logic changes the size should be under 500 lines. If the change is larger, explain whether it can be split into reviewable stages and identify the smallest coherent stage to land first. Base the staging suggestion on the actual diff, dependencies, and affected call sites.
More from openai/codex
- babysit-prBabysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep watching open PRs so fresh review feedback is surfaced promptly. Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.
- code-breaking-changesBreaking changes
- code-reviewRun a final code review on a pull request
- code-review-contextModel visible context
- code-review-testingTest authoring guidance
- codex-bugDiagnose GitHub bug reports in openai/codex. Use when given a GitHub issue URL from openai/codex and asked to decide next steps such as verifying against the repo, requesting more info, or explaining why it is not a bug; follow any additional user-provided instructions.
- codex-issue-digestRun a GitHub issue digest for openai/codex by feature-area labels, all areas, and configurable time windows. Use when asked to summarize recent Codex bug reports or enhancement requests, especially for owner-specific labels such as tui, exec, app, or similar areas.
- codex-pr-bodyUpdate the title and body of one or more pull requests.
- imagegenGenerate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG/vector/code-native assets, extending an established icon or logo system, or building the visual directly in HTML/CSS/canvas.
- openai-docsUse when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; use OpenAI docs MCP tools for non-Codex docs questions, use the Codex manual helper first for broad Codex self-knowledge, and restrict fallback browsing to official OpenAI domains.