Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Design: configurable second-reviewer loop

Aperta
  • Qualcosa non va?
#1,237 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
45/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python
Ambito
documentation

Direzione di ricerca

Start by reading the parent issue #1232 and the existing material in docs/design/ to understand the project’s design conventions. Write a design doc covering the reviewer interface, severity scale, round limits, finding ledger, stop rules, cost defaults, and gates; include sample .plate configs for Copilot and a local model, mark the multi-provider council as reference only, and list proposed follow-up issues. Done means every requirement in the issue is addressed in that document.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area:agent Design

Part of #1232.

Summary

Design a bounded second-reviewer loop. The ideas come from tstack's sol-loop and council skills (t3dotgg/tstack, MIT, credit Theo Browne). We write our own design.

Andrew's decision

Yes, but configurable. The reviewer is an adopter option: Copilot, a local model (for example via Ollama), OpenHands, Devin, or another tool. PLATE ships the interface, the round limit and the written-reason rules. PLATE does not hard-code a vendor. The three-model council stays reference only.

What the design must cover

  • Interface. How a reviewer is set (.plate setting), what it gets (base SHA, diff, intent, out of scope, check results), and the reply shape (verdict plus findings with stable ids).
  • Severity scale. blocker (intended case wrong), should (a real bug callers will hit), nit (the rest).
  • Round limit. Default 3 rounds. Up to 5 only for security, auth, data loss or concurrency while a blocker or should stays open. Stop early on nits only.
  • Ledger. Each finding gets an id, a severity and an outcome (fixed, disagree with evidence, or declined with a written reason).
  • Stop rules. Approved, or stuck after two replies on one item, or out of budget. Running out of budget is not approval. A timeout is not approval.
  • Cost defaults. Off or cheap by default. Read-only reviewers. One reviewer at a time.
  • Gates. The loop never merges and never overrides AGENTS.md approval gates.

Definition of done

  • A design doc in docs/design/ covers all points above, with a sample .plate config for at least Copilot and a local model.
  • It says the multi-provider council is reference only.
  • It lists follow-up implementation issues (proposed, not filed).
Lingua principale
Python
Stelle
1
Fork
0
Merge medio
2g 5h
PR unite (30g)
43

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di akasper/plate

Tutte le issue di akasper/plate

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.