메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Run isolated Moraine dev sandbox validation. Use when testing ingest, MCP, monitor, ClickHouse schema, source formats, stack behavior, or any change where QA must not touch the developer's host ~/.moraine install; use before reporting completion for stack-facing changes.
Help prepare and, only with explicit user approval, file a sanitized Moraine bug report for reproducible defects in Moraine itself.
Use Moraine realtime session data to inspect active agent work across harnesses when the user asks what is happening now or what another agent is doing.
Use Moraine MCP tools to recover prior agent-session context when the user refers to earlier work, decisions, failures, branches, files, or other agents.
Cut and publish Moraine releases from a version argument such as /release X.Y.Z or a request to use $moraine-dev:release. Use when Codex is asked to run Moraine's release process, bump release-managed versions, create and merge the release PR, push the vX.Y.Z tag, update GitHub release notes for a general audience, verify the release-moraine workflow, and confirm the PyPI moraine-cli package. Start or continue a Codex goal for the release.
Use Moraine MCP tools to recover prior agent-session context when the user refers to earlier work, decisions, failures, branches, files, or other agents.
| 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. |
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.
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.
Lead with scope crossings and the split or narrowing recommendation:
- [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.