phase: Skill for Claude Code

PR Review Loop

Continuously review open contributor PRs, reprocessing only when GitHub state indicates new information: changed head, author follow-up, stale approval, stale request-changes, CI transition, queue drop, or a policy/hard-stop condition.

This skill is intentionally small. Mutable policy and contributor-specific state do not live here.

Sources Of Truth

• GitHub is authoritative for PR head, author, reviews, comments, labels, CI, and merge-queue state.
• Repo policy lives in .agents/pr-review-policy.toml and must contain only repo-level, non-personal rules: path classifiers, domain capabilities, labels, hard-stop path patterns, generated-file patterns, and default gates.
• Local review memory lives outside the repo by default under ~/.local/state/pr-review/<owner>__<repo>/ unless PR_REVIEW_STATE_DIR or --state-dir is set. This directory contains:
  • review-events.jsonl — the sole canonical store: an append-only local event log with locked, deduplicated, fsync'd appends.
  • review-summary.json — generated token-minimal summary derived from the log.
  • review-dashboard.json — generated dashboard snapshot. It is a derived cache, not review memory: it combines the current open-PR scan with a retained terminal-PR archive so closed-without-merge PRs remain visible after the 48-hour active window.
  • github-discovery.json — disposable, versioned, repository-scoped raw GitHub discovery cache with the last successful query-start checkpoint. github-discovery.lock serializes the complete discovery/render/publish flow. Neither file is review memory or approval evidence; remove the cache or use --full-refresh to recover.
  • A stray review-state.sqlite from an older build is an orphaned leftover; it is no longer read or written, and is safe to ignore or delete manually.
• Never Read review-events.jsonl directly. It is unbounded and not token-shaped; all queries must go through the pr_review.py CLI (scan/inspect/recommend/analytics/compact). review-summary.json and the dashboard renderer's review-dashboard.json input are the only state files intended for direct reading.
• Repository writers bypass contributor-only gates. An author with write, maintain, or admin access (read live from GitHub's collaborator permissions, never from authorAssociation, which also reports triage-only collaborators as COLLABORATOR) is exempt from hard-stop path routing, architecture scope, frontend policy, and artifact admission; author_policy.repository_writer marks these packets. Their PRs still receive the full implementation review and the normal approval bar. When pr-contribution-handler is dispatched for one, pass the writer status so its path-based hard stops do not re-block the PR.
• No hardcoded names. Contributor standings, frontend exceptions, reviewer identities, private overrides, and one-off maintainer policy belong in local/private state, never in this skill.
• Contributor standing lives in private-overrides.json under contributor_standing (skip/probation/watch/trusted, lowercase-matched logins). It sits in the gitignored state dir on the review host; other hosts see only derived standing. The narrative quality log is a historical appendix — the event log, via recorded signals, is the data authority for per-contributor patterns.
• Gittensor PR-history enrichment is advisory. pr_review.py fetches the public Gittensor PR feed by default and adds a gittensor block to packets when the author appears there. A high closed-PR count across other repos adds the generic gittensor-closed-heavy proof risk flag. Use it to increase caution and require concrete proof; do not cite it as a public accusation or reject a PR on that signal alone.