corezoid-project-review

# 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 Check whether the workspace root contains a `<id>_<name>.stage.json` marker file (its `obj_id` is the stage ID). Practical test: call any Corezoid MCP tool with no arguments (e.g. `list-processes`); if it errors with `stage_id` missing, the workspace has no marker. - If the marker is **missing** → stop and invoke the `corezoid-init` skill. Do not proceed until init completes. - If present → use `obj_id` from the marker 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-Proces...