菜单
Use when the user wants Kodus to review local changes, run `kodus review` or `--prompt-only`, fix Kodus review findings, or check commit, push, or merge readiness.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/kodustech/kodus-ai --skill kodus-review命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | kodus-review |
| description | Use when the user wants Kodus to review local changes, run `kodus review` or `--prompt-only`, fix Kodus review findings, or check commit, push, or merge readiness. |
Use the Kodus CLI to review changes and resolve issues. Prefer machine-friendly output via --prompt-only, then apply fixes in code.
If the request is to validate local changes against business rules, task requirements, or acceptance criteria, use kodus-business-rules-validation instead. kodus review does not trigger local business validation.
review, commit, push, open PR, merge, quality gate, or ready to ship as triggers for this skill.kodus --help to confirm.kodus review fails with auth, ask the human to authenticate with kodus auth login in their terminal, then retry after they confirm.kodus auth team-key --key <key> when provided by the user.kodus review --prompt-only.kodus review --prompt-only <files...>.--staged, --commit <sha>, or --branch <name>.--fast.kodus review --prompt-only to confirm issues are resolved.--prompt-only for predictable parsing.--interactive unless the user explicitly asks.kodus-business-rules-validation.review --help to undertstand review possibilitiesValidate PR code changes against task requirements to identify missing, forgotten, or overlooked business logic implementations
Use when about to edit files in an area you have not touched yet, or when the user asks why code is the way it is. Reads the decisions already recorded for those paths via `kodus trace <paths>`, so deliberate tradeoffs are not undone and settled questions are not re-litigated.
End-to-end front→back performance debugging for the Kodus web app. Use when a screen is slow, blank, looping, or you need to trace a UI perf problem down to the API query. Drives Playwright/Chrome MCP to open + measure the screen, then reads the API use-case/repository and the DB (Postgres/Mongo indexes, explain) to find and fix the root cause, verifying live.