code-reviewer

A read-only code-review guide for checking a working change against its claimed behaviour. It focuses on correctness, related code, and tests rather than formatting or naming.

In plain words
What is it for?
Use it to inspect diffs, trace who calls changed code, check for failure cases such as missing errors or races, and report concrete findings with file locations.
Why use it?
It helps find defects and unintended effects without spending review time on issues handled by formatters or linters.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/rysh-ai/rysh-cli-code/code-reviewer
Any agent
npx skills add rysh-ai/rysh-cli-code --skill code-reviewer
Clone the repo
git clone --depth 1 https://github.com/rysh-ai/rysh-cli-code

Made for: Claude Code, Codex.

Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 264 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.00264
Opus 5 $0.00007 $0.00132
Sonnet 5 $0.00003 $0.00053
Haiku 4.5 $0.00001 $0.00026

Measured yesterday against content hash a70d4df1324e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-reviewer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

packages/code-reviewer/SKILL.md · 32 lines

What it actually says

You review code changes. You are read-only: you never edit, commit or push.

What to review

Read the diff first (git diff, or git diff --color=always when the human will read it). Then review for, in order:

  1. Correctness. Does it do what the change claims? Look for off-by-one errors, unhandled errors, nil dereferences, and races.
  2. Blast radius. What else calls this? Use grep and symbol_search rather than guessing.
  3. Tests. Does the change have a test that would fail without it? A test that passes either way is not coverage.

What not to review

Do not report formatting, naming preferences, or anything a linter owns. If the project has a formatter, assume it ran.

How to report

For each finding: the file and line, what breaks, and the input that breaks it. A finding you cannot state a failure case for is a hunch — say so, or drop it.

If the diff is fine, say so plainly. Do not manufacture findings to look thorough.

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 32 lines · 14 tokens per session scan A a70d4df1324e

Subscribe to this mod's changes

code-reviewer is a skill published in the GitHub repository rysh-ai/rysh-cli-code (5 stars, last pushed 15d ago), licensed Apache-2.0. It adds 14 tokens to every session and 264 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

openmaic-classroom

将 RAG 检索结果、文档块或知识图谱概念转换为 OpenMAIC 互动课程。当用户要求将知识库内容、检索到的文档片段、上传的文档、或知识图谱中的概念批量转换为教学课件/互动课堂时使用此技能。支持纯需求生成、基于 PDF 内容的课程生成、和基于概念图遍历的批量课堂生成。.

Tencent/WeKnora · 102 tokens

文档协作

引导用户通过结构化的文档共同编写工作流程。当用户想撰写文档、提案、技术规范、决策文档或类似结构化内容时使用。该工作流程帮助用户高效传递上下文,通过迭代优化内容,并验证文档对读者有效。当用户提到写文档、创建提案、起草规范或类似文档任务时触发。.

Tencent/WeKnora · 95 tokens

weknora-shared

Use when driving a WeKnora RAG server through the weknora CLI as an agent — authenticating, managing knowledge bases / documents / sessions / agents, running search or chat, or interpreting the CLI's JSON envelopes and exit codes. Read this before any other weknora- skill.

Tencent/WeKnora · 68 tokens

weknora-rag-search

Use when retrieving from or asking questions against a WeKnora knowledge base via the weknora CLI — and especially when unsure whether to use chat, session ask, or search chunks for a given goal.

Tencent/WeKnora · 54 tokens

数据处理器

数据处理与分析技能。当用户需要对知识库检索结果进行数据分析、统计计算、格式转换、数据提取或生成报告时使用此技能。支持 Python 脚本执行进行高级数据处理。.

Tencent/WeKnora · 51 tokens

文档分析器

深度分析文档结构和内容。当用户需要分析文档结构、提取关键信息、识别文档类型、进行内容质量评估、或理解文档组织方式时使用此技能。.

Tencent/WeKnora · 51 tokens