ds-review-loop

Installation
SKILL.md

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
    
Installs
60
GitHub Stars
5
First Seen
2 days ago