メニュー
Use when the user wants Kodus to review local changes through a local CLI build or non-production API such as `node dist/index.js`, localhost, or QA, including local `--prompt-only` flows.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/kodustech/kodus-ai --skill kodus-review-devコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
| name | kodus-review-dev |
| description | Use when the user wants Kodus to review local changes through a local CLI build or non-production API such as `node dist/index.js`, localhost, or QA, including local `--prompt-only` flows. |
Use the local Kodus CLI build in this repository 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. The local review command does not trigger local business validation.
review, commit, push, open PR, merge, quality gate, or ready to ship as triggers for this skill.skills/kodus-review-dev/scripts/run-local-cli.sh --help.kodus auth login in their terminal, then retry after they confirm.auth team-key --key <key> with the same helper script when provided by the user.skills/kodus-review-dev/scripts/run-local-cli.sh review --prompt-only.<files...>.--staged, --commit <sha>, or --branch <name>.--fast.skills/kodus-review-dev/scripts/run-local-cli.sh review --prompt-only to confirm issues are resolved.--prompt-only for predictable parsing.--interactive unless the user explicitly asks.kodus-business-rules-validation.KODUS_API_URL, KODUS_VERBOSE, and KODUS_CLI_ENTRYPOINT.--fix unless the user explicitly asks.Validate 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.