⚠️

重要前提

安装AI Skills的关键前提是：必须科学上网，且开启TUN模式，这一点至关重要，直接决定安装能否顺利完成，在此郑重提醒三遍：科学上网，科学上网，科学上网。查看完整安装教程 →

代码审查最佳实践指南：技术严谨性、验证优先、系统化流程 | 提升代码质量

code-review by siviter-xyz/dot-agent

60 周安装量

7 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/siviter-xyz/dot-agent --skill code-review

软件工程开发代码质量

🇨🇳中文介绍

代码审查

指导正确的代码审查实践，强调技术严谨性、基于证据的主张，以及验证优先于形式化回应。

概述

代码审查需要三种不同的实践：

接收反馈 - 技术评估优先于形式上的同意
请求审查 - 系统化的审查流程
验证关卡 - 任何完成声明之前都需要证据

核心原则

技术正确性高于社交舒适度。 实施前先验证。假设前先询问。主张前先提供证据。

何时使用

接收反馈

接收来自任何来源的代码审查意见时
反馈看起来不清晰或在技术上有疑问时
需要优先处理多个审查项时
外部审查者缺乏完整上下文时
建议与现有决策冲突时

请求审查

在子代理驱动的开发中完成任务后（在每个任务之后）
完成主要功能或重构时
合并到主分支之前
遇到瓶颈需要新视角时
修复复杂错误之后

验证关卡

即将声明测试通过、构建成功或工作完成时
提交、推送或创建 PR 之前
转移到下一个任务时
任何暗示成功/完成的声明时

快速决策树

    SITUATION?
    │
    ├─ Received feedback
    │  ├─ Unclear items? → STOP, ask for clarification first
    │  ├─ From human partner? → Understand, then implement
    │  └─ From external reviewer? → Verify technically before implementing
    │
    ├─ Completed work
    │  ├─ Major feature/task? → Request systematic review
    │  └─ Before merge? → Request systematic review
    │
    └─ About to claim status
       ├─ Have fresh verification? → State claim WITH evidence
       └─ No fresh verification? → RUN verification command first

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

🇺🇸English

Code Review

Guide proper code review practices emphasizing technical rigor, evidence-based claims, and verification over performative responses.

Overview

Code review requires three distinct practices:

Receiving feedback - Technical evaluation over performative agreement
Requesting reviews - Systematic review processes
Verification gates - Evidence before any completion claims

Core Principle

Technical correctness over social comfort. Verify before implementing. Ask before assuming. Evidence before claims.

When to Use

Receiving Feedback

Receiving code review comments from any source
Feedback seems unclear or technically questionable
Multiple review items need prioritization
External reviewer lacks full context
Suggestion conflicts with existing decisions

Requesting Review

Completing tasks in subagent-driven development (after EACH task)
Finishing major features or refactors
Before merging to main branch
Stuck and need fresh perspective
After fixing complex bugs

Verification Gates

About to claim tests pass, build succeeds, or work is complete
Before committing, pushing, or creating PRs
Moving to next task
Any statement suggesting success/completion

Quick Decision Tree

SITUATION?
│
├─ Received feedback
│  ├─ Unclear items? → STOP, ask for clarification first
│  ├─ From human partner? → Understand, then implement
│  └─ From external reviewer? → Verify technically before implementing
│
├─ Completed work
│  ├─ Major feature/task? → Request systematic review
│  └─ Before merge? → Request systematic review
│
└─ About to claim status
   ├─ Have fresh verification? → State claim WITH evidence
   └─ No fresh verification? → RUN verification command first

CI Verification

Before any completion claim or commit:

Run CI checks (types, tests, lint)
Prefer single CI command if available
Verify all checks pass
Do not proceed if checks fail

References

For detailed protocols, see:

references/receiving-feedback.md - How to handle code review feedback
references/requesting-review.md - Systematic review processes
references/verification-gates.md - Evidence before claims protocol

Weekly Installs

Repository

siviter-xyz/dot-agent

GitHub Stars

First Seen

Jan 20, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

cursor41

codex38

claude-code38

gemini-cli31

github-copilot30

opencode30