Guide

Pushing a good PR

A correct, focused, mergeable PR is the one that gets merged and paid. Here's how to make yours that one.

Work in your Koduo workspace

Claim the task and `koduo open` it. The workspace is scoped to the task's files and your branch, and commits land as koduo-ai[bot] on your behalf, so you don't need write access to the company's repo.

Match the acceptance criteria

The spec lists what 'done' means. Hit every criterion, because that's exactly what the company compares PRs against. If a criterion is ambiguous, resolve it in the PR description.

Keep the diff focused

Change only what the task needs. Drive-by refactors and unrelated formatting make a PR harder to review and slower to merge. One task, one coherent diff.

Test your change

Run the project's tests in the workspace before you push. A correct, mergeable PR with a green build is what gets merged; a failing build holds it up.

Write a clear PR description

Say what changed and why, and call out anything the reviewer should look at. `koduo pr create` opens it; `koduo pr checks` shows CI. No force-pushes on Koduo branches: a rewrite means a new branch and a new PR.

See the CLI reference for the full PR command set.