Files
nisse/nisse-review
dongarandClaude Opus 5.5 637761ba5a
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 1m41s
CI / e2e (pull_request) Successful in 7m41s
nisse-review: a retried or recovered review keeps its head's CI wait
From nisse-review's own review of #155: a failed run, a posted one and
crash recovery rebuilt the item without seen_at, so a retry skipped the
CI wait. seen_at now carries through, renewed when the head moved during
the review. Also: a test for checks Gitea can't report, and the example
config lists ci_wait_s and ci_grace_s.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J5Utyfzw7gF7UhjRDEtjTk
2026-10-17 04:35:05 +00:00
..
2026-10-13 22:34:02 +00:00

nisse-review

The Review Agent (Part R of the architecture): it reviews every pull request that is ready, in the repositories its Gitea account can read, and posts its review on the PR as a COMMENT review. It reads and comments; it never changes code, approves, or requests changes.

A thin application over nisse-core, with its own small scheduler:

  • config: its YAML configuration (nisse-review.example.yaml).
  • state: its state store, and a review item (one per PR).
  • scheduler: the duty (ready PRs), one review at a time, recovery after a crash.
  • reader: the repository at the PR's head and base, read-only, from Gitea's archives: the run's executor.
  • review: one review run, and posting it.
  • build, main: putting it together, and the access check at startup.

Bring-up on the development VM: scripts/review-bringup.sh.