Files
settled-reach/.claude/skills/pr-review/references/reviewer-profiles.md
T
jpmschweitzerandClaude Opus 4.8 05d7bffd6f docs(meta): repoint decisions/ paths to governance/ tree (pql migration)
Phase 1 follow-up: update the active instruction layer (CLAUDE.md, project
structure rule, DECISIONS.md redirect, agent personalities, skill docs) to
reference governance/{decisions,questions,rejected}/<domain>.md instead of the
retired flat decisions/*.md layout.

Path references only — command-surface references (tooling/db/decision*,
decisions-sync, Makefile targets, clerk) are repointed to the pql CLI in the
Phase 4 consumer cutover. Historical archives (docs/sprints, docs/discussions,
docs/workshops) keep their point-in-time decisions/ paths; the separate
whatsinagame/ template distribution is untouched. Agent-memory is gitignored
and out of scope.

The agent/skill repath was applied by tooling/pql-migrate/repath_references.py
(ordered, meaning-preserving replacements; bare-dir rule uses a negative
lookbehind so it can't corrupt a freshly-created governance/decisions/ path),
committed for provenance. CLAUDE.md, project-structure.md, and DECISIONS.md
were hand-edited (structural tree/table changes).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-06 12:18:49 +02:00

5.3 KiB

Reviewer Profiles by Branch Type

Use model: sonnet for all reviewers — sufficient for review, saves cost.

Reviewer agents read source files via git show or from sprint worktrees. Sprint branches use sprint-{N}/{team} naming. Include the branch name and a list of changed files in every prompt. The default approach is git show origin/<branch>:<path>. If an active worktree exists under .sprint/, agents can also use the Read tool with the worktree path. Always prefer git show over worktree reads — worktrees may use sparse checkouts that silently exclude files, causing reviewers to miss content and produce false findings (Sprint 33 lesson: Paula reported missing prose that was actually present, because the worktree excluded the wiki directory).

Code reviews (server, client, ci)

Hoshe (Code Quality)

  • subagent_type: hoshe, model: sonnet
  • Prompt: Provide the team directory path, list of changed files, and commit log. Tell Hoshe to read source files from the team directory, then review for:
    • Correctness and bug risks
    • Error handling gaps
    • Test coverage (are new features tested?)
    • Code style and clarity
    • Security concerns (OWASP top 10, injection risks)
    • Performance issues

Tyre (Architecture)

  • subagent_type: tyre, model: sonnet
  • Prompt: Provide the team directory path, list of changed files, and commit log. Tell Tyre to read the relevant governance/**/*.md files from the team directory first, then review for:
    • Architectural consistency with project decisions
    • API/interface design quality
    • Dependency and coupling concerns
    • Scalability implications
    • Whether the change respects non-negotiable baselines (D-010, D-012)

Copy reviews (copy)

Hoshe (QA)

  • subagent_type: hoshe, model: sonnet
  • Prompt: Provide the team directory path, list of changed files, and commit log. Tell Hoshe to read the changed files from the team directory, then review for:
    • Formatting consistency (markdown, file naming, frontmatter)
    • Broken references or links
    • Spelling and grammar
    • File organization and structure
    • Missing or orphaned files

Paula (Narrative Depth)

  • subagent_type: paula, model: sonnet
  • Prompt: Provide the team directory path, list of changed files, commit log, and list of relevant governance/**/*.md files to read. Tell Paula to read all files from the team directory using the Read tool, then review for:
    • Narrative quality and character voice consistency
    • Whether dialogue and monologue feel authentic to the characters
    • Consequences and stakes — do choices carry weight?
    • Political and interpersonal depth
    • Emotional resonance — does the text make you feel something?

Miri (World Consistency)

  • subagent_type: miri, model: sonnet
  • Prompt: Provide the team directory path, list of changed files, commit log, and list of relevant governance/**/*.md files to read. Tell Miri to read all files from the team directory using the Read tool, then review for:
    • Lore accuracy — do facts match established setting?
    • Internal consistency across files
    • IP originality — nothing should read as a copy from another franchise
    • Faction, technology, and location details match the worldbuilding docs
    • Setting serves gameplay mechanics (asymmetric information, perception)

Visual reviews (visual)

Hoshe (QA)

  • subagent_type: hoshe, model: sonnet
  • Prompt: Provide the team directory path, list of changed files, and commit log. Tell Hoshe to read the changed files from the team directory, then review for:
    • File format and naming conventions
    • Asset organization and directory structure
    • Missing or broken references in scene/resource files
    • Import settings consistency

Araminta (Art Direction)

  • subagent_type: araminta, model: sonnet
  • Prompt: Provide the team directory path, list of changed files, and commit log. Tell Araminta to read the style guide and relevant design docs from the worktree first, then review for:
    • Visual consistency with the established style guide
    • Color palette adherence
    • UI pattern consistency (diegetic-first, clarity over beauty)
    • Whether assets scale gracefully (boxes-with-labels to full-art)
    • Mood and tone — sleek, advanced, subtle Settled Reach aesthetic

Audio reviews (audio)

Hoshe (QA)

  • subagent_type: hoshe, model: sonnet
  • Prompt: Provide the team directory path, list of changed files, and commit log. Tell Hoshe to read the changed files from the team directory, then review for:
    • File format and naming conventions
    • Audio asset organization and directory structure
    • Missing or broken references
    • Import/bus configuration consistency

Ozzie (Player Experience)

  • subagent_type: ozzie, model: sonnet
  • Prompt: Provide the team directory path, list of changed files, and commit log. Tell Ozzie to read all files from the team directory using the Read tool, then review for:
    • Emotional impact — does the audio enhance the moment?
    • Atmosphere and tone — does it feel like the Settled Reach?
    • Player feedback clarity — can the player tell what just happened?
    • Pacing — do sounds support or fight the gameplay rhythm?
    • Memorable moments — will players remember these audio cues?