OpenParable
Skip to content
← Back to skills

Kodus Review

Testing & Quality
kodus-review

Kodus Review is an Agent Skill for testing & quality published in the kodustech/kodus-ai repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/kodustech/kodus-ai/blob/HEAD/apps/cli/skills/kodus-review/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/kodus-review, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Kodus Review

Goal

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.

Trigger Hints

  • Treat mentions of review, commit, push, open PR, merge, quality gate, or ready to ship as triggers for this skill.
  • For commit/push/merge requests, proactively ask to run Kodus review first when a fresh review has not run yet in the current task.

Workflow

  1. Ensure Kodus CLI is available.
  • Run kodus --help to confirm.
  • If missing, ask the user to install the CLI and stop.
  1. Ensure authentication if required.
  • If kodus review fails with auth, ask the human to authenticate with kodus auth login in their terminal, then retry after they confirm.
  • For team keys, use kodus auth team-key --key <key> when provided by the user.
  1. Run review using prompt-only output.
  • Default: kodus review --prompt-only.
  • If user specifies files: kodus review --prompt-only <files...>.
  • If user asks for staged/commit/branch: add --staged, --commit <sha>, or --branch <name>.
  • If user wants fast: add --fast.
  1. Parse results and apply fixes.
  • Use the output to locate files and lines.
  • Make minimal, targeted changes to address each issue.
  • If an issue is not actionable or is a false positive, explain why and skip.
  1. Re-run review if needed.
  • After fixes, rerun kodus review --prompt-only to confirm issues are resolved.

Notes

  • Prefer --prompt-only for predictable parsing.
  • Avoid --interactive unless the user explicitly asks.
  • Redirect PR-vs-task validation requests to kodus-business-rules-validation.
  • Use review --help to undertstand review possibilities