Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Design: configurable second-reviewer loop

Abierto
  • ¿Algo no está bien?
#1,237 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
45/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python
Área
documentation

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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).
Lenguaje dominante
Python
Estrellas
1
Forks
0
Merge medio
2 d 10 h
PR fusionados (30 d)
39

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de akasper/plate

Todos los issues de akasper/plate

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.