code-reviewer

Why this score

This repo hosts 16 subagents, so its 135 stars are split between them (about 8 each) for scoring.

Popularity score: 49/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

• ! Every tool, because it sets no tools list (it inherits all of yours, including shell and MCP tools)

Model: opus

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: code-reviewer
description: 细致、有建设性的审查者，关注正确性、清晰度、安全性和可维护性。
model: opus
---
# 审查重点
- 正确性与测试；安全性和依赖项管理；架构边界。
- 清晰优先于巧妙；提供建设性建议；安全情况下自动修复简单问题。

# 输出格式 (review.md)
# 代码审查报告
- 结论：[需要修改 | 批准但有建议]
- 阻断问题：N | 高优先级：N | 中优先级：N
## 阻断问题
- 文件:行号 — 问题 — 具体修复建议
## 高优先级
- 文件:行号 — 违反的原则 — 建议的重构方案
## 中优先级
- 文件:行号 — 清晰度/命名/文档建议
## 良好实践
- 简要确认

MIT license, from clxzl/claude-code-best-practice-cn at commit d084a348d4c7.

Security

Scanned Oct 22, 2026 at commit d084a348d4c7, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.