メニュー
A read-only code-review mode. Inspect a diff or branch and report correctness bugs and quality issues (reuse, simplification, efficiency) WITHOUT modifying files. Use when asked to review a PR/diff, confirm a fix is sound, or do a focused quality pass before committing.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
创建/管理"持续运转的家庭任务"—— 由 rule（条件触发自动化）/ schedule（定时提醒）/ record（行为累积统计）/ lifecycle（长期/限时）组合装配；也是 [感知引擎] 语音指令类系统消息的统一入口。覆盖：定时/累积提醒、"X 时 Y" 自动化、行为统计、持续状态阈值等。
查询与控制米家智能家居设备。查询能力包括设备开关状态、运行状态、电量、设定温度、当前温湿度、PM2.5 等环境与设备数据；控制能力包括开关灯、调节空调温度/模式/风速、控制窗帘开合、启动或停止扫地机器人、开关摄像头等设备操作；场景能力包括触发已有米家场景，如回家、离家、睡眠等智能场景；以及刷新设备列表缓存。
每日习惯洞察 —— 从家庭档案识别值得建成任务的习惯，主动 IM 推荐给主人；主人认可后据此建任务。两条路径：cron 触发的【扫描推荐】(路径 A) 与用户回应触发的【回应处理】(路径 B)。防骚扰由 miloco_habit_suggest 工具裁定。
home-dreaming 定时任务的 Observe 步骤，仅由该任务调用。
miloco-home-patrol 定时任务的内部例程，仅由该任务调用。
家庭档案管理 — 当用户提到自己或家人的喜好、兴趣、习惯、身体状况、作息规律、家庭规则时激活，无论用户是否明确要求"记录"。也在用户修正已有记录、要求删除、或查询家庭档案时激活。
| name | review-mode |
| description | A read-only code-review mode. Inspect a diff or branch and report correctness bugs and quality issues (reuse, simplification, efficiency) WITHOUT modifying files. Use when asked to review a PR/diff, confirm a fix is sound, or do a focused quality pass before committing. |
review-mode is a focused, read-only working mode for reviewing code changes.
It mirrors the behaviour of the Claude Code runtime's built-in review mode: while
it is active you analyse and report, but you do not edit files, run mutating
commands, or commit.
read_file, list_dir, search_context and read-only
shell commands (git diff, git log, git status, git show). Do not call
write_file, do not run mutating commands, do not commit or push.git diff, or git diff <base>...<head>), then reason about what the change
does and what it touches. Review the change, not the whole repository.file:line for every finding and quote the
relevant code. Never invent issues; if you are unsure, say so and explain how
to verify. Calibrate effort to what was asked (a few high-confidence findings
for a quick pass; broader coverage for a deep review).Group findings by severity. For each finding give: location (file:line), a
one-line summary, why it matters, and a concrete suggested fix. End with a short
overall verdict (e.g. looks good, minor nits, needs changes before merge).
If the user then asks you to apply fixes, leave review mode and make the edits.