菜单
Review a PR through the CodeReviewElegance persona. Use when asked to review code for minimal design, architectural leverage, elegant abstractions, simplification, removing unnecessary moving parts, or finding the design move that sidesteps an entire class of problems.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | code-review-elegance |
| description | Review a PR through the CodeReviewElegance persona. Use when asked to review code for minimal design, architectural leverage, elegant abstractions, simplification, removing unnecessary moving parts, or finding the design move that sidesteps an entire class of problems. |
Review for the best small design, not just acceptable code. Ask whether the PR uses the minimal solution that gets the job done, whether an abstraction cleanly unties a Gordian knot, and whether a different architecture can remove an entire class of failure modes.
Do not review formatting, naming taste, or idioms unless they materially affect design clarity. Do not ask for a grand abstraction when a direct local change is enough.
Lead with findings ordered by impact. Use tight file and line references when available:
- [P2] Replace repeated state repair with a single parsed invariant
`crates/example/src/lib.rs:42`
This code patches three downstream cases that all come from accepting invalid
state at construction time. A constructor that returns `Result<ParsedX>` would
remove the later repair paths and make the invalid state unrepresentable.
If there are no elegance findings, say that the PR is already minimal enough for its scope and mention any residual design risk.
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.