Skip to main content

​
Overview

The recursive-review-bundle subskill generates a durable, reproducible context bundle before you delegate an audit or review to a subagent. Without a canonical bundle, delegated reviews are context-free and cannot be accepted by the recursive-mode workflow. 
npx skills add try-works/recursive-mode --skill recursive-review-bundle --full-depth

​
When to Use

Use this subskill whenever you are delegating a Phase 3.5 code review, test review, or other audit to a subagent. Generate the bundle before dispatching the reviewer, and refresh it after any material repairs or scope changes.
This subskill packages the handoff context. It does not replace the canonical workflow in /.recursive/RECURSIVE.md and it does not perform the review itself.

​
The Canonical Scripts

Two scripts ship with recursive-mode for generating review bundles:
  • scripts/recursive-review-bundle.py — use when Python is available
  • scripts/recursive-review-bundle.ps1 — use when the delegated path is PowerShell-oriented
Prefer the Python script when both toolchains are available.

​
Minimum Required Inputs

Every bundle invocation must include all of the following:
InputDescription
repo rootPath to the repository root
run idThe current recursive-mode run ID
phase nameThe phase being reviewed (e.g., 03.5 Code Review)
reviewer roleThe canonical role (e.g., code-reviewer)
artifact pathPath to the artifact being reviewed
upstream artifactsExact paths to all artifacts the reviewer must re-read
audit questionsThe specific questions the review must answer
required output shapeThe format the reviewer’s output must take
Add evidence refs or addenda paths explicitly when they are relevant — the bundle generator will also auto-discover applicable addenda and skill-memory refs.

​
Commands

python scripts/recursive-review-bundle.py \
  --repo-root . \
  --run-id "<run-id>" \
  --phase "03.5 Code Review" \
  --role code-reviewer \
  --artifact-path "/.recursive/run/<run-id>/03.5-code-review.md" \
  --upstream-artifact "/.recursive/run/<run-id>/00-requirements.md" \
  --upstream-artifact "/.recursive/run/<run-id>/02-to-be-plan.md" \
  --audit-question "Which R# remain incomplete?" \
  --required-output "Findings ordered by severity"

​
Acceptance Rules

After generating the bundle, follow these rules before and after delegation:
1

Record the bundle path

Record Review Bundle Path in the delegated phase artifact. Without a recorded path, the phase cannot be considered properly delegated.
2

Require the reviewer to cite the bundle

The reviewer must reference the bundle path, name the upstream artifacts they re-read, cite relevant addenda, reference the changed files or code they reviewed, and provide a final verdict. A bare bundle file is not proof of review quality — the written review must use the bundle contents.
3

Refresh after repairs

If material repairs or scope changes occur after the bundle was generated, regenerate it before sending to the reviewer. A stale bundle invalidates the review.
Do not treat a delegated review as accepted if the reviewer’s output does not cite the bundle, upstream artifacts, and changed files. Generic summaries with no grounded findings must be rejected. See the Subagent page for the full output rejection checklist.

​
Bundle Location

Canonical bundles are stored under: 
/.recursive/run/<run-id>/evidence/review-bundles/
Reference this path in the phase artifact and in the handoff to the subagent so the review is durable and repeatable across sessions.