recursive-review-bundle

Generate canonical review bundles from run artifacts and routing configurations.

128|10|Updated Apr 6, 2026

Search Tags:#workflow #audit #delegation #review #code-review #bundle #recursive-mode

Ready to run

npx skills add https://github.com/try-works/recursive-mode --skill recursive-review-bundle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: recursive-review-bundle
Source: https://github.com/try-works/recursive-mode/tree/main/skills/recursive-review-bundle
Command: npx skills add https://github.com/try-works/recursive-mode --skill recursive-review-bundle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill packages the context bundle that delegated reviewers need so the review is durable, reproducible, and acceptable to the workflow, enabling canonical delegated audits or reviews in recursive-mode.

Core Features & Use Cases

Canonical review bundle generation for Phase 3.5 code reviews, test reviews, or other delegated checks.
Supports both Python and PowerShell scripts located in ./scripts/ to generate the bundle.
Integrates with existing run artifacts and routing configurations to ensure traceability and auditable handoffs.

Quick Start

Execute the Python or PowerShell generator to produce a canonical review bundle for the current run using the repository root and run-id.

Frequently Asked Questions about recursive-review-bundle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a reproducible review bundle for a delegated code audit?▼

A canonical review bundle packages the exact context, run artifacts, and routing configurations a delegated reviewer needs so the audit remains durable, reproducible, and traceable across recursive-mode workflow phases.

How do I generate a canonical review bundle using Python or PowerShell?▼

You generate a canonical review bundle by executing the Python or PowerShell scripts located in the scripts directory, passing required inputs like repo-root, run-id, phase, role, and artifact paths to output a bundle path and phase artifact record.

What inputs are required to generate a review bundle for Phase 3.5 workflows?▼

Generating a review bundle for Phase 3.5 workflows requires inputs including the repository root, run-id, phase, role, and artifact paths to ensure proper traceability and auditable handoffs during delegated checks.

Does the review bundle generator work without existing run artifacts?▼

The review bundle generator leverages existing run artifacts and configuration files to ensure traceability, meaning it requires these pre-existing phase outputs to package a durable and acceptable context bundle for delegated reviewers.

When do I need to package a canonical review bundle for code reviews?▼

You need to package a canonical review bundle when performing delegated audits, code reviews, or deliverable validations in recursive-mode, ensuring the delegated reviewer receives a reproducible context that meets workflow standards.