跳到主内容
智客 ZICQ

技能库 智客分类:安全测试 review

Review

使用新鲜剂审查执行变化而无需编辑. 检查行为、安全性、回归性、复杂性、测试、文件以及缺失的证据。 用于代码,PR,diff,security,second-opinion,或前置评论.

691 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

使用新鲜剂审查执行变化而无需编辑. 检查行为、安全性、回归性、复杂性、测试、文件以及缺失的证据。 用于代码,PR,diff,security,second-opinion,或前置评论.

何时用

官方 description 未单独写出 Use when。按规范,代理会在用户任务与这段 description 的关键词匹配时激活本技能。

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Review、Scope、Standard、Review order、Code review findings、Verdict。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Uses a fresh agent to review an implementation change without editing it. Checks behavior, security, regressions, complexity, tests, docs, and missing proof. Use for code, PR, diff, security, second-opinion, or pre-merge reviews.

ReviewScopeStandardReview orderCode review findingsVerdictBoundaries

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
review
description
Uses a fresh agent to review an implementation change without editing it. Checks behavior, security, regressions, complexity, tests, docs, and missing proof. Use for code, PR, diff, security, second-opinion, or pre-merge reviews.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「review」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-68bbe502ee40fdcd-%E5%AE%A1%E6%9F%A5.html
请存为 .cursor/skills/review/SKILL.md 或 .claude/skills/review/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/owainlewis/blueprint' --list

npx skills add 'https://github.com/owainlewis/blueprint' --skill 'review'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版

name: review description: "Uses a fresh agent to review an implementation change without editing it. Checks behavior, security, regressions, complexity, tests, docs, and missing proof. Use for code, PR, diff, security, second-opinion, or pre-merge reviews." user-invocable: true argument-hint: "[diff, branch, commit, PR, or file path]"

Review

Find defects that can change the result or make the change unsafe. Do not turn personal taste into a finding.

Use a fresh subagent that did not implement the change. Stay read-only. Do not edit files or post comments.

Scope

Review the implementation target named by the user. It may be a file, diff, branch, commit, pull request, or other code change on GitHub. Use /architecture-review for a technical proposal that has not been implemented.

If the user does not name a target, review the repository's complete local change set. Include commits on the current branch relative to the default branch, staged changes, unstaged changes, and untracked files.

Use the repository and the immediate surrounding code as context. If there are no local changes, say so. Do not substitute a whole-repository audit.

Standard

Approve only when:

  • The change matches its source and behaves as required.
  • No known defect or unhandled risk could break the source or repository rules for security, data loss, compatibility, or operations.

Do not demand perfection or block on personal taste. Cite technical evidence or repository conventions.

The verdict is independent agent evidence. It is not GitHub approval or a replacement for human review.

Review order

  1. Set the frame. Give the reviewer the task, acceptance criteria and invariant IDs from its task or design, repository rules, complete diff or pull request, and test evidence. Name the user or developer affected by the change.
  2. Take the broad view. Read the change summary and the relevant design or ticket. Confirm that the change belongs in the system, matches the intended behavior, and delivers one reviewable outcome. Report a mismatch before reviewing details.
  3. Review the main behavior. Start with the files and flows that deliver the outcome. Check behavior, failures, security boundaries, interfaces, compatibility, migrations, concurrency, and operations.
  4. Review every human-written changed line in context. Read enough surrounding code to judge correctness, regressions, complexity, names, comments, style, and docs. For generated files or large data, inspect the source and spot-check the output. Keep findings within the change's scope.
  5. Review the proof. Check that tests:
    • Cover the changed behavior and affected failure paths.
    • Prove every cited AC-n, INV-n, or task criterion.
    • Assert behavior a user or caller can observe, or a documented internal contract.
    • Would fail under a broken implementation.
    • Do not copy implementation logic or hide the scenario in setup.
  6. Run focused checks that can confirm or disprove a claim that could change a finding or verdict.
  7. Check specialist coverage. Identify security, privacy, concurrency, accessibility, internationalization, or domain-specific work. Mark a risk unverified when the reviewer lacks the evidence or skill to judge it. Use Blocked when that gap could hide a problem that breaks a rule and no qualified reviewer covers it.
  8. Report findings. Return actionable findings in priority order using the format below.

Code review findings

Report only real bugs, customer-impacting problems, and proven simplifications introduced or exposed by the change. Check security, logic, behavior, reliability, compatibility, regressions, and affected failure paths.

Inspect enough surrounding code to prove each finding. A simplification must deliver the same result and proof with less state, indirection, duplication, or operational work. Report it only as Could fix.

Use this format for every finding:

Priority: Must fix / Should fix / Could fix
Confidence: 0 to 5
What I found: Describe the technical problem.
Why it matters: Explain the impact on customers, callers, or the service.
Trigger and effect: State the exact condition and what the customer or service experiences.
Where: File and line.
Suggested fix: Give a short, practical direction.

Priority means:

  • Must fix: Unsafe to merge. The change can cause a security failure, data loss, broken required behavior, or a serious service regression.
  • Should fix: A real defect or reliability risk that should be corrected before merge.
  • Could fix: A proven, limited problem or simplification that does not need to block merge. Do not use this for style preferences.

Confidence means:

  • 5: Confirmed by reproduction, test, or direct code evidence.
  • 4: Strong evidence with no credible alternative explanation.
  • 3: Probable, but some runtime evidence is unavailable.
  • 0 to 2: Do not report. Investigate further or mark the area unverified.

Use plain words. State what breaks, when it breaks, and who it affects. Omit style preferences, theoretical concerns, and problems outside the change.

Verdict

If fresh subagents are unavailable, stop and report that independent review is blocked unless the user explicitly accepts a documented self-review.

If there are no findings, say so. End with Approve, Request changes, or Blocked, then state what remains unverified. A Must fix or Should fix finding requires Request changes. Could fix findings do not prevent Approve.

Boundaries

  • Keep findings within the change, but inspect enough surrounding code to judge each changed line and its system effect.
  • Do not turn preferences into findings. Use technical evidence and repository conventions.
  • Do not approve solely because checks pass.

相关技能

安全测试

Skill Vetter

人工智能特工的安全第一技能审查。 在安装来自 ClawdHub, GitHub 或其他来源的任何技能之前使用 。 检查红旗,许可范围,可疑图案.

安全测试

Moltguard

MoltGuard——由OpenGuardrails担任OpenClaw保安. 安装 MoltGuard 以保护你和你的人类免受迅速注射、数据过滤和恶意命令的影响。 资料来源:https://github.com/openguardrails/openguardrails/tre…

安全测试

Security Auditor

用于审查安全漏洞代码,实施认证流,审计OWASP Top 10,配置CORS/CSP头,处理秘密,输入验证,SQL注射预防,XSS保护,或任何与安全相关的代码审查.

安全测试

Skill Vetter

安装任何AI代理技能前的安全审查协议. 红旗侦取入证盗取,疏通密码,放出. 风险分类:低/中/高/高。 编制结构化审查报告。 不先运行此功能, 绝不安装不信任的技能 .