메뉴
Review a PR through the CodeReviewCompleteness persona. Use when asked to check whether a PR fully addresses the objectives it claims to address in its title, description, cited issue, PRD, epic, acceptance criteria, or linked discussion.
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-completeness |
| description | Review a PR through the CodeReviewCompleteness persona. Use when asked to check whether a PR fully addresses the objectives it claims to address in its title, description, cited issue, PRD, epic, acceptance criteria, or linked discussion. |
Review against the stated objective. Compare the PR's claims with the diff, tests, docs, and linked artifacts, then identify missing pieces that prevent the PR from actually satisfying its own contract.
Do not expand the PR's scope beyond its stated objective. Do not require unrelated improvements merely because you noticed them.
Lead with missing objective coverage:
- [P1] Add the documented MCP behavior test
`docs/example.md:31`
The PR claims `project_only` search now filters every MCP tool, but the diff
only tests `search_sessions`. Add coverage for `open` or narrow the PR claim.
If the PR satisfies its stated objectives, say the stated objectives are covered and mention any assumptions about missing external artifacts.