code-review-scope
/code-review-scope
Review a PR through the CodeReviewScope persona. Use when asked to check whether a PR stays within its intended scope, avoids crossing into unrelated topics, separates incidental cleanup from behavior changes, and keeps review lanes clear.
- Author
- eric-tramel ↗
- Repository
- moraine ↗
- Licence
- Apache-2.0
- Last repository change
- 10.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Review a PR through the CodeReviewScope persona. Use when asked to check whether a PR stays within its intended scope, avoids crossing into unrelated topics, separates incidental cleanup from behavior changes, and keeps review lanes clear.
Original author description
Review a PR through the CodeReviewScope persona. Use when asked to check whether a PR stays within its intended scope, avoids crossing into unrelated topics, separates incidental cleanup from behavior changes, and keeps review lanes clear.
How it works
- Persona
- Focus
- Non-Goals
- Output
SKILL.md preview
--- name: code-review-scope description: Review a PR through the CodeReviewScope persona. Use when asked to check whether a PR stays within its intended scope, avoids crossing into unrelated topics, separates incidental cleanup from behavior changes, and keeps review lanes clear. --- # CodeReviewScope ## Persona Review for scope control. Compare the stated purpose with the actual diff and call out unrelated changes that make the PR harder to review, test, or revert. ## Focus - Identify files, modules, migrations, config, docs, or UI changes that do not support the stated goal. - Separate required enabling changes from opportunistic cleanup. - Flag mixed concerns such as feature work plus broad refactors, formatting churn, dependency changes, or unrelated docs updates. - Check whether operational impact, migrations, and behavior changes are disclosed in the PR body. - Recommend splitting only when it reduces review risk or deployment risk. ## Non-Goals Do not block small local cleanup that directly clarifies the changed code. Do not require splitting changes that are tightly coupled and safer to land together. ## Output Lead with scope crossings and the split or narrowing recommendation: ```markdown - [P2] Split the monitor restyle from the MCP filtering fix `web/monitor/styles.css:1` The PR is scoped to MCP project filtering, but half the diff changes monitor colors and spacing. Moving the restyle to a separate PR keeps the filtering fix easier to review and revert. ``` If there are no scope findings, say the PR stays within its stated scope.
Files in this package (2)
- SKILL.md 2 KB
- agents/openai.yaml 1 KB
Versions
The database has no other skills named code-review-scope.
Database snapshot: 13.11.2026 · package version feb14e052b1b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100code-review-yagni
Review a PR through the CodeReviewYAGNI persona. Use when asked to check whether a PR stays focused on the task, avoids overengineering, avoids premature generalization, and does not defensively program around edges that are not expected to occur. - 100code-review-idomatic
Review a PR through the CodeReviewIdomatic persona. Use when asked to check whether code is idiomatic for the implementation language, follows standard library and ecosystem conventions, avoids unnecessarily novel implementations, and matches established patterns in this repository. - 90scope-check
Checks that requested work stays inside the active spec boundary. Use when an implementation, refactor or bug fix could quietly grow past the approved story or solution. - 95pr
Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue. - 90code-review
Run evidence-based code review for a pull request, branch diff, or local changes. Use when the user requests CR, code review, re-review, or a bounded review-and-fix loop and needs actionable findings and a clear readiness decision. Not a whole-repository audit or a style-only cleanup workflow. - 90code-review
Review code changes for correctness, regressions, and unintended scope. Use when reviewing a pull request, branch, commit, patch, or local diff, including when invoked with /code-review.