cf-review-in

Solid

Collect and act on review results from an external AI agent. Reads the result file written by an external reviewer and presents findings, then offers to fix issues. Use when the user wants to collect an outside review — e.g. "review in", "collect review", "check review results", "cf-review-in", "read external review", "import review".

Code & Development 3 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 79/100

Stars 20%
20
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# $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 Custom guide — auto-loaded below (if the raw command shows instead of its output, run it yourself): ```! bash "${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...

Details

Author
dinhanhthi
Repository
dinhanhthi/coding-friend
Created
5 months ago
Last Updated
today
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

cf-review-out

Generate a review prompt for an external AI agent. Creates a self-contained document that any AI (Gemini, Codex, ChatGPT, or even a human) can read and use to review your code changes. Use when the user wants an outside review — e.g. "get a second opinion", "external review", "review out", "send for review", "cf-review-out", "outside review", "prepare review for gemini", "review prompt".

3 Updated today
dinhanhthi
Code & Development Solid

cf-review

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.

3 Updated today
dinhanhthi
Code & Development Listed

ce-review

Independently code-review implemented code — auto-detecting which direction the review runs. Outbound mode (the default): walk six lenses (correctness, security, performance, maintainability, conformance, simplicity) over a feature's diff with an adversarial verification pass. Inbound mode (PR review comments pasted in): treat each human comment as a CLAIMED finding, verify it against the code (substantiated / refuted / unverifiable), and draft paste-ready replies. Findings, never patches; escalates. Posts to no forge, edits no code. Triggers: code-review/audit the quality or security of a built feature, or triage/answer pasted human PR review comments. Asks HOW IT'S WRITTEN; for DOES IT BEHAVE use /ce-verify. Auto-detects outbound vs inbound from the pasted payload — you need not say which.

0 Updated 4 days ago
relusion