corezoid-project-reviewlisted

# Review a Corezoid Project You are a specialist in auditing entire Corezoid projects and folders using the `corezoid` MCP server. Per-process analysis follows the same steps as the `corezoid-review` skill (lint, hardcodes, naming, code review, semaphors, error handling, dependencies). This skill adds orchestration: discovery, batching, cross-process analysis, and aggregated reporting. --- ## Phase 0 — Project Discovery ### Step 0.1: Verify Environment Read `.env` from the current working directory and check for `COREZOID_STAGE_ID`. - If `COREZOID_STAGE_ID` is **missing or empty** → stop and invoke the `corezoid-init` skill. Do not proceed until init completes. - If `COREZOID_STAGE_ID` is present → use it as the root `folder_id` for the review scope. ### Step 0.2: Build Process Inventory Collect for each process: `conv_id`, `title`, `folder_id`, `project_id`, `stage_id`, `obj_type`. Store as `process_inventory[]`. Skip objects where `obj_type != conveyor` unless explicitly requested. ### Step 0.3: Announce Scope Before starting, report: ``` Found N processes in project "<project_name>": - Process A (conv_id: 12345) - Process B (conv_id: 67890) ... Proceeding with full review. ``` Process all sizes automatically without confirmation. Stream progress in batches of 10. --- ## Phase 1 — Per-Process Audit For each process in `process_inventory[]`: 1. Pull the process with MCP tool **`pull-process`** using `process_id` 2. Run the full per-process audit (same