cf-review-inlisted

# /cf-review-in > **CLI Requirement:** OPTIONAL — Uses the memory MCP from `coding-friend-cli` for fast indexed search and storage. Without the CLI: falls back to grep over `docs/memory/` and direct file writes. Full functionality preserved, slower memory recall. See [CLI requirements](../../../docs/cli-requirements.md). Collect external review results for: **$ARGUMENTS** ## Purpose Reads the review results written by an external AI agent (generated via [`/cf-review-out`](/docs/skills/cf-review-out/)) and presents them in the conversation. Then offers to fix any issues found. ## Workflow ### Step 0: Custom Guide Run: `bash "${CLAUDE_PLUGIN_ROOT}/lib/load-custom-guide.sh" cf-review-in` If output is not empty, integrate returned sections: `## Before` → before first step, `## Rules` → apply throughout, `## After` → after final step. ### Step 1: Determine the label and optional service Parse `$ARGUMENTS` as `<label> [service]` — label is required, service is optional. If `$ARGUMENTS` contains a label (and optionally a service), use them. Otherwise: - List available result files in `<docsDir>/reviews/` that match `*-result-*.md` - Extract unique labels from the filenames. Two formats are supported: - New format: `YYYY-MM-DD-<label>-result-<service>.md` — the full `YYYY-MM-DD-<label>` stem is the label - Legacy format: `<label>-result-<service>.md` — the `<label>` stem is the label - If exactly one label exists, use it - If multiple labels exist, ask the user which