aicodeking/deepseek-stack

ds-review-loop

Runs an author and a fresh-context reviewer in a loop on the current change until both agree it is correct, for at most four rounds.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-review-loop

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

Make a change more correct by letting one fresh reviewer push back until you both agree.

Steps

  1. Scope the change. Run git status --short. Do not stash, discard or include unrelated files. Find the base: git fetch origin, then git merge-base HEAD origin/<base branch>. Use one diff command for every round.
  2. Write the goal and out-of-scope list in two sentences. Run the covering checks. Do not send code that fails them.
  3. Pick the reviewer: a stronger model if the harness can reach one (subagent with a model setting, team worker, second CLI), or else a fresh DeepSeek context with no history. Record which one.
  4. Send this brief:
   Review only. Do not edit, commit, push, comment or start subagents.
   Repo: <path>  Base: <sha>  Diff: git diff <sha> [-- <paths>]
   Goal: <goal>  Out of scope: <list>  Checks: <results>
   Read the code around the diff. Find bugs, broken callers and gaps against the goal.
   Flag code the goal does not need. Ignore style unless it hides a bug.
   blocker = goal case is wrong. should = real bug users will hit. nit = anything else.
   Reply: VERDICT: APPROVE or CHANGES, then one line per finding:
   R1 [blocker|should|nit] file:line claim. Fix: suggestion
  1. Wait for the reply. Do not edit the scoped files while the review runs. A timeout or error is not approval.
  2. Judge each finding yourself. Agree: make the smallest fix, preferring to delete or narrow code. Disagree: reply with evidence (file:line, test output). Nit or out of scope: decline in one line.
  3. Keep a ledger: id, severity, outcome, evidence. Re-run checks and git diff --shortstat. If the diff grew, cut it back.
  4. For the next round send the brief, the ledger and the changes since the last round. Ask the reviewer to check only open ids and changed code.

Stop when

  • The reviewer returns APPROVE on the current diff, no blocker or should is open, and you have no concern left.
  • A round returns only nits.
  • Four rounds are done, or one item stays disputed after two exchanges. Report both sides in two or three lines each and let the user decide. This is not approval.

Rules

  • One reviewer at a time. Never agree just to end the loop.
  • Do not push during the loop. Push afterward only if the user asked to push or ship.
  • If you update a PR, add: Reviewed with ds-review-loop: <N> rounds, <reviewer>, verdict <verdict>.
  • Report rounds, reviewer, fixed and declined findings with reasons, and diff size before and after.
aus demselben Repository

Weitere Skills

Alle Skills
aicodeking
Community

ds-adopt

Takes over an existing PR, branch or agent thread and finishes its original goal while keeping credit for the first contributors. Use when the user says take over, adopt, pick up or finish this PR, or /ds-adopt.

Installationen / 1h
2
GitHub Stars
75
Aktualisiert
28. Okt.
aicodeking
Community

ds-best-of-n

Run N independent attempts at the same task in parallel, pick the strongest as the base, and graft the best parts of the others into it. Use when one attempt at a non-trivial artifact could land on the wrong shape, or for /ds-best-of-n, 'try a few versions', 'best of 3'.

Installationen / 1h
2
GitHub Stars
75
Aktualisiert
28. Okt.
aicodeking
Community

ds-blast-radius

Find what a change could break outside its own diff, then prove the key safety fact by running real code. Use before shipping a risky or untrusted change, for 'what could this break', 'blast radius of X', or /ds-blast-radius.

Installationen / 1h
2
GitHub Stars
75
Aktualisiert
28. Okt.
aicodeking
Community

ds-blueprint

Design the types, function signatures and module layout first, agree on that shape, then implement against it. Use when work is non-trivial and coding straight away would lock in the wrong structure, or for /ds-blueprint, 'design this first', 'architect this'.

Installationen / 1h
2
GitHub Stars
75
Aktualisiert
28. Okt.