Come usare
- Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
- Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
- Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-juryPrima di iniziare
- L’installazione non include abbonamenti, quote API o accesso ai file.
- Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale
Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.
Get two or three independent reviewers to judge the same change, then fix until they agree.
Steps
- Get the work ready first. Answer open PR comments, fix known issues and run the relevant checks. Skip this only if the user wants to throw the code away.
- Pick the jurors. Use models the user named. Otherwise pick the strongest available model from two or three different providers, at high reasoning effort.
- Find a way to reach them in this harness: team workers or subagents with a model setting, a second agent CLI in the terminal (for example a Codex or Claude CLI), or an API call. If only one model is available, start two or three fresh-context subagents of that model, each with a different persona: correctness, security and edge cases, simplicity and scope.
- Write one brief for all jurors: repo path, base SHA, diff command, goal in one sentence, out-of-scope items and check results. Tell them to review only and change nothing.
- Ask each juror for: a verdict (APPROVE or CHANGES), a score out of 10 and findings as
id severity file:line claim fix. Severity is blocker, should or nit. - Run the jurors in parallel. Wait for all of them. A timeout or error is not approval.
- Check each finding against the code yourself. Fix the ones you agree with, with the smallest change. Write a one-line reason for each one you reject.
- Re-run checks. Start a new round with the same brief, your answers and the new diff.
- Report the result. If there is a PR, edit its description and add a table: juror, model, score per round. Write
no scorewhen a juror gave none. If there is no PR, put the table in your final reply.
Stop when
- Every juror returns APPROVE with no open blocker or should finding.
- Three rounds are done. Report the open disagreements, with both sides in two lines each. The user decides.
- A round returns only nits. Stop without another round.
Rules
- Jurors are read-only. They do not edit, push, comment or start their own subagents.
- Say which jurors are the same model as each other. Do not claim a provider you did not reach.
- Never invent a score or verdict.
- Guard the scope. Decline new features and list them as follow-ups.
