菜单
Use when the user wants a product/design/UX critique (e.g. "product-review", "/product-review", "is this the right thing to build / the right UX?"). Questions what to build and how users will perceive it, not just code correctness.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when the user asks to take a task end-to-end autonomously (e.g. "autodev", "/autodev", "build this on autopilot"). Runs the full chain — plan → implement → review → PR → converge — stopping only at real decisions.
Use when the user asks for a cross-review by Claude (e.g. types "claude-review", "/claude-review", or "have Claude review this"). Invokes Claude Code headlessly to review the current branch/changes, prints Claude's findings verbatim, then triages them skeptically instead of auto-agreeing.
Use when the user wants the current code proactively reviewed and fixed (e.g. "review-loop", "/review-loop", "review what I have and fix it"). Self + cross-model review → triage → fix → update PR, loop until clean.
Use when the user asks to plan a task before coding (e.g. "plan-loop", "/plan-loop", "plan this out first"). Draft a detailed plan, cross-review it with Claude, triage skeptically, iterate, then gate for sign-off.
| name | product-review |
| description | Use when the user wants a product/design/UX critique (e.g. "product-review", "/product-review", "is this the right thing to build / the right UX?"). Questions what to build and how users will perceive it, not just code correctness. |
| metadata | {"short-description":"Critique what & how to build, not just whether it's correct"} |
Product/design/UX critique — same workflow as Claude's /product-review.
Canonical procedure: read ~/.codex/skills/skyhook-skills-commands/product-review.md and follow it
(premise → journeys (8–10, ranked 0–10) → UX shape → comprehension → states →
AI-slop/design-system → 0–10 + "what a 10 looks like" + severity triage). Codex
notes:
.claude/commands/qa.md).