← ClaudeAtlas

cf-reviewlisted

Dispatch code review to a subagent. Use when the user wants code reviewed — e.g. "review this", "review my changes", "check the code", "look over this", "code review", "any issues with this?", "is this code ok?", "review before merge", "review the diff", "what do you think of these changes?". Also triggers on requests to review specific files, commits, or branches.
dinhanhthi/coding-friend · ★ 2 · Code & Development · score 71
Install: claude install-skill dinhanhthi/coding-friend
# /cf-review > **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). > ✨ **CODING FRIEND** → /cf-review activated Review the code changes for: **$ARGUMENTS** ## Auto-Triggered This skill is automatically invoked by other skills — you don't always need to run it manually: - **`/cf-plan`** — runs `/cf-review` after all implementation tasks complete - **`/cf-fix`** — runs `/cf-review` after the fix is verified - **`/cf-optimize`** — runs `/cf-review` after the optimization is measured and verified ## Workflow ### Step 0: Custom Guide Run: `bash "${CLAUDE_PLUGIN_ROOT}/lib/load-custom-guide.sh" cf-review` If output is not empty, integrate returned sections: `## Before` → before first step, `## Rules` → apply throughout, `## After` → after final step. ### Step 1: Identify the target - If `$ARGUMENTS` is empty, review all uncommitted changes (`git diff` + `git diff --staged`) - If `$ARGUMENTS` is a file path, review that file - If `$ARGUMENTS` is a commit range (e.g., `HEAD~3..HEAD`), review those commits - If `$ARGUMENTS` is a natural language description (e.g., "the auth logic changes"), review all uncommitted changes but **focus the review** on the described area — filter findings to only report issues relevant to that de