菜单
Review changes made for a single step of an orrery plan (YAML file under the orrery plans directory) when invoked by the orrery orchestrator, and produce structured feedback for the editor agent. Do NOT use for general code review outside of an orrery plan run.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Author an orrery plan — a YAML file under the orrery plans directory that the orrery CLI executes step-by-step. Use ONLY when the user explicitly asks to create an orrery plan (e.g., "make an orrery plan", "use orrery discovery", "/discovery"). Do NOT use for general planning, architectural discussion, or decomposing ideas unless the output is an orrery plan file.
Implement a single step from an orrery plan (YAML file under the orrery plans directory) when invoked by the orrery orchestrator. Do NOT use for general coding, bug fixes, or implementation work outside of an orrery plan run.
Final reporting phase for a single step of an orrery plan, invoked by the orrery orchestrator after orrery-verify completes (or when reporting blocked status). Outputs structured JSON consumed by the orrery orchestrator. Do NOT use for general status summaries or reports outside of an orrery plan run.
Verify a single step from an orrery plan (YAML file under the orrery plans directory) when invoked by the orrery orchestrator after orrery-execute. Runs the plan step's acceptance criteria, tests, and linting. Do NOT use for general test runs, linting, or verification work outside of an orrery plan run.
Analyze and improve an existing orrery plan (YAML file under the orrery plans directory). Reviews plan structure, dependencies, context quality, and acceptance criteria, then edits the plan file directly. Use ONLY when the user explicitly asks to refine an orrery plan and provides a plan file argument (e.g., /refine-plan my-plan.yaml). Run `orrery plans-dir` to find the plans directory. Do NOT use for general plan or design-doc review.
Explore an existing orrery plan (YAML file under the orrery plans directory) through conversational dialogue before committing to execution. Use ONLY when the user explicitly asks to simulate an orrery plan and provides a plan file argument (e.g., /simulate-plan my-plan.yaml, /simulate-plan my-plan). Run `orrery plans-dir` to find the plans directory. Do NOT use for general "what if" brainstorming outside of an orrery plan.
| name | orrery-review |
| description | Review changes made for a single step of an orrery plan (YAML file under the orrery plans directory) when invoked by the orrery orchestrator, and produce structured feedback for the editor agent. Do NOT use for general code review outside of an orrery plan run. |
| user-invocable | false |
Use this skill after a step execution to review the changes and provide feedback to an editor agent.
Triggers:
Do not apply fixes yourself. Only review and report.
For every modified or added file, read the full file contents to understand broader context. Do not review only the diff.
Check the changes against these criteria:
approved if there are no blocking issues.needs_changes if any blocking issue exists.Return a single JSON object to stdout.
{
"status": "approved | needs_changes",
"feedback": [
{
"file": "path/to/file.js",
"line": 42,
"severity": "blocking | suggestion",
"comment": "Explain the issue and expected fix."
}
]
}
Rules:
line is optional if not applicable.feedback may be empty only when status is approved.Scenario: Missing null check in src/service.js.
{
"status": "needs_changes",
"feedback": [
{
"file": "src/service.js",
"line": 87,
"severity": "blocking",
"comment": "Guard against null `user` before accessing `user.id` to avoid runtime errors."
}
]
}