// 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.
| 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.Use when the user wants to create, update or view Kody Rules via `kodus rules` command.
Use when the user wants to manage centralized configuration via `kodus config centralized` commands (status, init, sync, disable, and download).
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 when the user wants Kodus to validate local diff changes against task requirements, acceptance criteria, or business rules via `kodus pr business-validation`, especially for implementation-vs-task or merge readiness checks.
Use when the user wants to fetch, triage, or implement Kodus suggestions for an existing remote pull request via `kodus pr suggestions`, `--pr-url`, or `--pr-number`.