Files
nisse/nisse-review
dongarandClaude Opus 5.5 faf973be6c
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 1m48s
CI / e2e (pull_request) Successful in 28m44s
nisse-review: match repository patterns against Gitea's search
At bring-up, `dev/*` failed: listing an organization's repositories
(/orgs/dev/repos) needs the read:organization token scope, which the
reviewer's token doesn't have and shouldn't need. Patterns are now matched
against /repos/search, which needs only the repository scope and already
lists every repository the account can read. A pattern that matches
nothing is logged (access.no_match). owner_repositories goes.

A Gitea error at startup is now reported like a config error, not a
traceback.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J5Utyfzw7gF7UhjRDEtjTk
2026-10-16 22:17:47 +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.