Reviewing changes
Esta página aún no está disponible en tu idioma.
Nothing leaves a session until you have reviewed it. The right pane of the dashboard — and the matching commands — is built for exactly this.
All files
Section titled “All files”The files in the session, including ones the agent added:
chronos session files <id>Changes
Section titled “Changes”A per-file summary of what changed versus your base branch: the status (Added, Modified, Deleted) and how many lines were added or removed. Open a file to read the full diff.
chronos session changes <id> # +/− per filechronos session diff <id> # the full diff vs baseChecks
Section titled “Checks”Checks are your verification steps — the tests, linting, or quality gates your project defines. They are how you confirm a session is sound before it goes anywhere.
chronos session check <id> # run your checks nowIn the dashboard:
- The Checks tab shows the last result, so it opens instantly.
- Run checks runs them again and shows each step’s outcome, plus the details of anything that failed.
- An overall: green / red banner summarizes the run. Red blocks merge.
Because results are kept, you can revisit a session later and still see whether it was green.
What review-ready means
Section titled “What review-ready means”A session is ready to ship when:
- The changes are what you intended.
- Checks are green.
- You are confident in the result.
Only then do the approval and merge actions unlock — see Pull requests, approvals, and merge.