mcpField
D
ds-review-loop

ds-review-loop

github.com/aicodekingテスト・品質263440 回インストール2 週間前に更新
リポジトリ

ds-review-loop について

ds-review-loopは、範囲を限定したコード変更を、履歴のない1人のレビュアーに繰り返し確認してもらうレビュー用ワークフロースキルです。確認、指摘の判断、対応記録、終了条件を定めています。

主な機能

  1. 01変更範囲の設定とチェック実行
  2. 02独立した重点レビューの依頼
  3. 03指摘の分類と評価
  4. 04根拠に基づく判断の記録
  5. 05各ラウンド後の変更再確認

活用シーン

  1. 01提出前のコード変更レビュー
  2. 02報告された不具合の最小修正
  3. 03異議や却下を含むレビュー指摘の記録

インストール

コマンドをコピーしてターミナルで実行します。

$npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-review-loop

インストール後、Claude Code で/ds-review-loopを入力して読み込まれたか確認します。

README（原文）English

プロジェクトの README より

この README の日本語訳はまだありません。以下は英語の原文です。日本語の紹介はページ上部をご覧ください。

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

  5. Wait for the reply. Do not edit the scoped files while the review runs. A timeout or error is not approval.

  6. 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.

  7. Keep a ledger: id, severity, outcome, evidence. Re-run checks and git diff --shortstat. If the diff grew, cut it back.

  8. 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.

コメント

Markdown 対応