ワンクリックでManusで任意のスキルを実行

recursive-review-bundle

スター56

フォーク2

更新日2026年4月12日 01:48

Use when recursive-mode work needs a canonical delegated-review or audit handoff. Generates reproducible review bundles for Phase 3.5 code review, test review, or other delegated checks using the repo review-bundle scripts.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

try-works

try-works/role-model

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

recursive-review-bundle

Use this skill to prepare a canonical review bundle before delegating an audit or review in recursive-mode.

This skill does not replace /.recursive/RECURSIVE.md. It packages the context bundle that delegated reviewers need so the review is durable, reproducible, and acceptable to the workflow.

Canonical Scripts

Use the repo scripts:

../../scripts/recursive-review-bundle.py
../../scripts/recursive-review-bundle.ps1

Prefer the Python script when both toolchains are available. Use the PowerShell wrapper when the delegated path is already PowerShell-oriented.

Minimum Inputs

Provide all of:

repo root
run id
phase name
reviewer role
artifact path being reviewed
exact upstream artifact paths
relevant audit questions
required output shape

Add explicit evidence refs or addenda when they matter. The bundle generator will also auto-discover relevant addenda and skill-memory refs when applicable.

Typical 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"

pwsh -NoProfile -File ../../scripts/recursive-review-bundle.ps1 `
  -RepoRoot . `
  -RunId "<run-id>" `
  -Phase "03.5 Code Review" `
  -Role code-reviewer `
  -ArtifactPath "/.recursive/run/<run-id>/03.5-code-review.md" `
  -UpstreamArtifact "/.recursive/run/<run-id>/00-requirements.md","/.recursive/run/<run-id>/02-to-be-plan.md" `
  -AuditQuestion "Which R# remain incomplete?" `
  -RequiredOutput "Findings ordered by severity"

Acceptance Rules

Record Review Bundle Path in the delegated phase artifact.
Refresh the bundle after material repairs or scope changes.
Require the reviewer to cite the bundle path, upstream artifacts reread, relevant addenda, changed files or code refs reviewed, and a final verdict.
Do not treat a bare bundle file as proof of review quality; the written review still has to use the bundle contents.

References

/.recursive/RECURSIVE.md
../../docs/templates/commands/recursive-review-bundle.md
../../skills/recursive-subagent/SKILL.md

このリポジトリの他の Skills

同じリポジトリ

contributing

try-works/role-model

Use when contributing to the Cloudflare Docs repository — writing or editing documentation pages, choosing content types or components, adding changelog entries, reviewing docs, or learning how to contribute.

2026-07-1156

style-guide-review

try-works/role-model

Review changed MDX/docs files in a pull request against the Cloudflare docs style guide and return structured findings.

2026-07-1156

turnstile-spin

try-works/role-model

Set up Cloudflare Turnstile end-to-end in a project — scan the codebase, create the widget via the Cloudflare API, deploy the managed siteverify Worker, write the frontend snippets, validate, and persist the skill. Load this when a user asks to add Turnstile, set up CAPTCHA, protect a form from bots, or fix a Turnstile integration. Mirrors developers.cloudflare.com/turnstile/spin.

2026-07-1156

recursive-mode

try-works/role-model

Repository workflow orchestration skill for staged implementation, locked artifacts, late-phase receipts, and durable memory maintenance. Use when executing recursive-mode runs, resuming a run, locking a phase, or verifying locks.

2026-07-1056

role-model

try-works/role-model

Use when Pi should route model requests through a locally running Role-Model runtime, inspect Role-Model aliases, or diagnose Role-Model provider setup.

2026-06-2856

ui-design-system

try-works/role-model

React UI component systems with TailwindCSS + Radix + shadcn/ui. Stack: TailwindCSS (styling), Radix UI (primitives), shadcn/ui (components), React/Next.js. Capabilities: design system architecture, accessible components, responsive layouts, theming, dark mode, component composition. Actions: review, design, build, improve, refactor UI components. Keywords: TailwindCSS, Radix UI, shadcn/ui, design system, component library, accessibility, ARIA, responsive, dark mode, theming, CSS variables, component architecture, atomic design, design tokens, variant, slot, composition. Use when: building component libraries, implementing shadcn/ui, creating accessible UIs, setting up design systems, adding dark mode/theming, reviewing UI component architecture.

2026-05-1156

name	recursive-review-bundle
description	Use when recursive-mode work needs a canonical delegated-review or audit handoff. Generates reproducible review bundles for Phase 3.5 code review, test review, or other delegated checks using the repo review-bundle scripts.

recursive-review-bundle

Use this skill to prepare a canonical review bundle before delegating an audit or review in recursive-mode.

This skill does not replace /.recursive/RECURSIVE.md. It packages the context bundle that delegated reviewers need so the review is durable, reproducible, and acceptable to the workflow.

Canonical Scripts

Use the repo scripts:

../../scripts/recursive-review-bundle.py
../../scripts/recursive-review-bundle.ps1

Prefer the Python script when both toolchains are available. Use the PowerShell wrapper when the delegated path is already PowerShell-oriented.

Minimum Inputs

Provide all of:

repo root
run id
phase name
reviewer role
artifact path being reviewed
exact upstream artifact paths
relevant audit questions
required output shape

Add explicit evidence refs or addenda when they matter. The bundle generator will also auto-discover relevant addenda and skill-memory refs when applicable.

Typical 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"

pwsh -NoProfile -File ../../scripts/recursive-review-bundle.ps1 `
  -RepoRoot . `
  -RunId "<run-id>" `
  -Phase "03.5 Code Review" `
  -Role code-reviewer `
  -ArtifactPath "/.recursive/run/<run-id>/03.5-code-review.md" `
  -UpstreamArtifact "/.recursive/run/<run-id>/00-requirements.md","/.recursive/run/<run-id>/02-to-be-plan.md" `
  -AuditQuestion "Which R# remain incomplete?" `
  -RequiredOutput "Findings ordered by severity"

Acceptance Rules

Record Review Bundle Path in the delegated phase artifact.
Refresh the bundle after material repairs or scope changes.
Require the reviewer to cite the bundle path, upstream artifacts reread, relevant addenda, changed files or code refs reviewed, and a final verdict.
Do not treat a bare bundle file as proof of review quality; the written review still has to use the bundle contents.

References

/.recursive/RECURSIVE.md
../../docs/templates/commands/recursive-review-bundle.md
../../skills/recursive-subagent/SKILL.md