claude-reviewlisted

Use when Codex needs a read-only local Claude Code review of work Codex prepared, including current git diffs, staged changes, exact commits, specific branch diffs against a base ref, scoped changed paths, explicit local files, specs, design docs, ignored files, or final pre-response quality checks. Routes through the global `claude-review` CLI instead of calling `claude` directly.
valkrisd/claude-review · ★ 0 · Code & Development · score 70

Install: claude install-skill valkrisd/claude-review

# Claude Review Use this skill to ask the user's local Claude Code CLI for one strict, read-only review pass over Codex-written changes. Codex remains the implementer and final decision maker. ## Commands Use the globally installed CLI: ```bash claude-review setup claude-review review claude-review review --base main claude-review review --branch feature/payments --base main claude-review review --commit abc1234 claude-review review --commit abc1234 --context-files docs/design.md claude-review review --paths src tests claude-review review --context-files docs/design.md claude-review files docs/design.md docs/api.yaml claude-review review --scope staged claude-review review --focus "billing permissions and migrations" claude-review usage ``` ## Workflow 1. Run the user's normal verification first when practical: tests, lint, type checks, or the narrow command relevant to the change. 2. Run `claude-review review` for local working-tree changes, `claude-review review --base <ref>` for current `HEAD` against a base, `--branch <ref> --base <ref>` for a specific branch, or `--commit <ref>` for exactly one commit. 3. Use `--paths` only to narrow git changes. Use `--context-files <file...>` for local specs/design docs that Claude should use as requirements while reviewing the selected code. Use `claude-review files <file...>` when the files themselves are the review target, including ignored files inside the current workspace. Scoping is explicit: use `-