Back to Skills

interactive-code-review

verified

Human-in-the-loop code review with chunk-by-chunk approve/reject/chat loop (git add -p style). Use when reviewing PRs, diffs, patches, or documents interactively. Triggers on "review my PR", "walk through changes", "interactive review".

View on GitHub

Marketplace

moo.md

saadshahd/moo.md

Plugin

hope

core

Repository

saadshahd/moo.md
28stars

hope/skills/interactive-code-review/SKILL.md

Last Verified

February 5, 2026

Install Skill

Select agents to install to:

Scope:
npx add-skill https://github.com/saadshahd/moo.md/blob/main/hope/skills/interactive-code-review/SKILL.md -a claude-code --skill interactive-code-review

Installation paths:

Claude
.claude/skills/interactive-code-review/
Powered by add-skill CLI

Instructions

# Interactive Code Review

Run a structured, interactive review session that presents changes in small, readable chunks and waits for the human to approve, reject, or chat before moving on.

## Framework

Structured Walkthrough: author intent is surfaced first, then the reviewer probes for risks, gaps, and misunderstandings. Established software quality practice (IEEE 1028) for defect detection and shared understanding.

## Workflow

1. **Confirm target and intent.**
   - Ask for the diff source if unclear (branch range, file paths, or patch).
   - Clarify what "good" looks like (correctness, style, performance, risk).

2. **Gather material.**
   - For code: `git status -sb`, `git diff --stat`, then `git diff <base>...<head>`.
   - For documents: ask for the text, sections, or relevant excerpt.

3. **Chunk the review.**
   - File-by-file, then hunk-by-hunk within each file.
   - Target 40–120 lines per chunk. Split large hunks.
   - Order: module boundaries (entry points, public interfaces) first, then internals, finally tests.
   - For prose: split by headings or logical paragraphs.

4. **Present each chunk** with the standard template. Pause for explicit response.

5. **Handle responses.**
   - **Approve**: mark approved, continue.
   - **Reject**: explain issue, propose concrete edit, confirm before changing files.
   - **Chat**: answer questions, show context. Re-prompt with same actions. Chat loops until user gives approve/reject/skip.
   - **Skip**: mark for later, continue.
   - **Done**: end review immediately, show summary.
   - **Jump [file]**: skip to specific file.

6. **Wrap up with summary.**
   - List approved, rejected, skipped chunks.
   - Offer to apply edits or re-run on updated diffs.

## Actions

| Action | Aliases | Effect |
|--------|---------|--------|
| approve | ok, lgtm, yes, y, +1 | Mark approved, continue |
| reject | no, fix, change, -1 | Explain issue, propose edit |
| chat | ?, context, explain, why | More context, re-prompt |
| skip 

Validation Details

Front Matter
Required Fields
Valid Name Format
Valid Description
Has Sections
Allowed Tools
Instruction Length:
4054 chars