Prompt file imported from B0yZ4kr14/OrthoPlus-Enterprise (.github/prompts/speckit.multi.model.review.apply.review.prompt.md). Fill in {{arguments}} before use. Copyright stays with the author.

speckit.multi.model.review.apply.review

Description

Instructions

name: speckit-multi-model-review-apply-review description: Ingest the reviewer's review-report.md and drive remediation, optionally using configured subagent routing for accepted fixes. compatibility: Requires spec-kit project structure with .specify/ directory metadata: author: github-spec-kit source: multi-model-review:commands/apply-review.md

speckit.multi-model-review.apply-review

Spec Kit extension command: /speckit.multi-model-review.apply-review

Legacy Claude plugin command: /multi-model-review:apply-review

Consume a reviewer agent's review-report.md and walk through the findings.

Arguments: {{arguments}}

Steps

1. Locate the package.

   • If {{arguments}} contains a path, use it.
   • Else pick the latest .cross-review/packages/*/ that contains review-report.md.
   • If none exist, abort with: "No review-report.md found. Did the reviewer save its output?"

2. Parse review-report.md using .specify/templates/review-report.md.

   • Context sufficiency
   • Verdict
   • Summary
   • findings with:
     • severity
     • confidence
     • location
     • summary
     • detail
     • suggested_fix
   • Read metadata.json when present for:
     • subagent_routing
     • selected implementation model/options
     • package scope and path filters

3. Handle context sufficiency first.

   • If Context sufficiency = needs-full-package:
     • present the current findings
     • do not start broad edits yet
     • recommend /multi-model-review:review-package --full
     • if the findings are clearly path-local, recommend /multi-model-review:review-package --paths <subset>
     • stop unless the user explicitly wants to continue with the current report

4. Filter findings.

   • Default: drop findings with confidence < 70
   • --min-confidence N overrides
   • Group remaining findings by severity, then file

5. Present a numbered checklist.

   • Quote the reviewer's wording instead of paraphrasing it
   • Do not edit files yet

6. For each finding the user accepts:

   • read the target file at the cited line
   • propose one edit for that finding
   • if subagent_routing.mode = auto and the accepted finding is path-local, route the fix to mmr-implementation-worker
   • if the finding is cross-cutting, ambiguous, migration-heavy, or security-sensitive, ask mmr-heavy-planner for a remediation plan before editing
   • apply only after confirmation
   • if two findings touch the same line, re-read between edits
   • record status in .cross-review/packages/<pkg>/review-state.json

7. After the pass:

   • if subagent routing is enabled and changes were made, run mmr-review-checker for a read-only local preflight when the scope is small enough
   • summarize applied vs skipped findings
   • remind the user that a re-review means:
     • /multi-model-review:review-package
     • run the reviewer again

Guardrails

• Never auto-apply a critical finding without explicit confirmation.
• Never merge multiple findings into one edit.
• If the compact package was declared insufficient, prefer re-packaging before broad remediation.
• Do not use subagents to bypass user confirmation for review fixes.

Context

• Project: OrthoPlus Enterprise
• Auto-generated from: .kimi/skills/speckit-multi-model-review-apply-review/SKILL.md
• Synced: 2026-05-24T21:37:04-03:00