Load personas from target repo .review-bot/personas/ #60

Closed
opened 2026-05-11 01:57:13 +00:00 by rodin · 0 comments
Owner

What

Allow repos to define their own personas by placing YAML files in .review-bot/personas/.

Why

Different repos have different domain concerns:

  • gargoyle needs trading/event-sourcing experts
  • kms-lite needs crypto/key-management experts
  • generic repos can use built-in personas

Implementation

  1. Before running review, check if target repo has .review-bot/personas/ directory
  2. If yes, load personas from there (YAML format)
  3. If no, fall back to built-in personas
  4. Merge with built-in personas (repo personas take precedence on name collision)

Acceptance Criteria

  • Fetch .review-bot/personas/*.yaml from target repo via Gitea API
  • Parse YAML personas with same schema as built-in
  • Fall back to built-in if directory missing or empty
  • Tests for persona loading from remote repo
## What Allow repos to define their own personas by placing YAML files in `.review-bot/personas/`. ## Why Different repos have different domain concerns: - gargoyle needs trading/event-sourcing experts - kms-lite needs crypto/key-management experts - generic repos can use built-in personas ## Implementation 1. Before running review, check if target repo has `.review-bot/personas/` directory 2. If yes, load personas from there (YAML format) 3. If no, fall back to built-in personas 4. Merge with built-in personas (repo personas take precedence on name collision) ## Acceptance Criteria - [ ] Fetch `.review-bot/personas/*.yaml` from target repo via Gitea API - [ ] Parse YAML personas with same schema as built-in - [ ] Fall back to built-in if directory missing or empty - [ ] Tests for persona loading from remote repo
rodin added the wip label 2026-05-11 02:02:07 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: rodin/review-bot#60