Agent Skills › UniClipboard/UniClipboard › review-strict

review-strict

GitHub

对当前分支或工作区变更进行严格、基于证据的代码审查，不修改文件。重点检查正确性、安全、架构及测试覆盖，按严重程度输出发现并提供合并评估建议。

.agents/skills/review-strict/SKILL.md UniClipboard/UniClipboard

触发场景

用户要求进行严格审查、深度审查或高级审查用户询问合并评估结果显式调用 $review-strict

安装

npx skills add UniClipboard/UniClipboard --skill review-strict -g -y

更多选项

非标准路径

npx skills add https://github.com/UniClipboard/UniClipboard/tree/v1/.agents/skills/review-strict -g -y

不安装直接使用

npx skills use UniClipboard/UniClipboard@review-strict

指定 Agent (Claude Code)

npx skills add UniClipboard/UniClipboard --skill review-strict -a claude-code -g -y

安装 repo 全部 skill

npx skills add UniClipboard/UniClipboard --all -g -y

预览 repo 内 skill

npx skills add UniClipboard/UniClipboard --list

SKILL.md

Frontmatter

{
    "name": "review-strict",
    "description": "Perform a strict, evidence-based review of the current branch or working-tree changes without modifying files. Use when the user asks for a strict review, deep review, senior review, merge assessment, or explicitly invokes `$review-strict`."
}

Strict Code Review

Review the current diff first. Inspect unchanged code only when it is necessary to establish the behavior of a changed path.

Prioritize:

Correctness, regressions, state transitions, edge cases, concurrency, cleanup, compatibility, and performance.
Security and privacy, especially plaintext persistence, sensitive logs, excessive permissions, clipboard data exposure, authentication reuse, and raw paths.
Repository architecture, ownership, existing reusable modules, hard-coded values, dead code, and parallel old/new logic.
Cross-platform behavior on macOS, Windows, Linux, iOS, Android, and HarmonyOS where the changed path applies.
Missing or ineffective tests, including duplicated hand-written mocks where an established test helper exists.

For every finding:

Cite the file and exact line.
State the concrete trigger as input or state -> incorrect behavior.
Explain why it matters and the smallest sound correction.
Try to disprove the finding before retaining it.

Order findings by severity: blocking, important, optional. Do not report style preferences or speculative issues. If no real issue remains, say so clearly and note any residual verification gap.

End with one merge assessment: ready to merge, merge after fixes, redesign required, or insufficient evidence. Do not edit, commit, or push.