dev-review
Skill1 starsChanged yesterdayMITView on GitHub
独立代码审查、本地严苛预审、不可信外部 PR 供应链拦截、行为/结构双门与门型评估,以及六锁防死循环收敛。 触发词:代码审查、审一下改动、审查 PR、本地预审、提交前审查、检查 diff、审外部 PR、 供应链扫描、故障注入审查、复审、打回返工、review、pre-review、untrusted scan。
7 other projects use a version of this.
Adopted by
Most recently taken up by
- baekenough/oh-my-customcodetheir own version, first seen Nov 14, 2026
- codeaholicguy/ai-devkittheir own version, first seen Nov 12, 2026
- boman-ng/skillstheir own version, first seen Oct 25, 2026
- TchiRubick/skillstheir own version, first seen Oct 20, 2026
- egoxx1/unified-master-harnesstheir own version, first seen Oct 11, 2026
- alanshurafa/co-evolutiontheir own version, first seen Sep 17, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- codeaholicguy/ai-devkit★ 1.7ksame name
- baekenough/oh-my-customcode★ 42same name
- alanshurafa/co-evolution★ 4same name
- boman-ng/skills★ 2same name
- egoxx1/unified-master-harness★ 1same name
- TchiRubick/skills★ 1same name
- codihaus/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- dev-exploreSkill
- dev-flowSkill
- dev-governSkill
- dev-planSkill
- project-forgeSkill
The file
Files
dev-review:评审 → 实证测试-形式验证 → 验收 双门六锁把关器
承接 dev-flow submit 提审或本地预审,把「独立审查子代理调用」与「开发者本地日常预审」统一到只读打包与记账入口:
node .agents/skills/dev-review/scripts/review-pack.mjs,并在记账时向 signals.jsonl 沉淀处置信号供 dev-govern retro 复盘进化。
双重模式与入口命令
先运行打包脚本生成上下文隔离的审查包,再开始判读与测试:
# 模式 A:flow 独立审查子代理 / 外部 PR(支持自动推断 --task 与下一 --round,Tier 2 自动同步 review-<id> 并挂载依赖)
node .agents/skills/dev-review/scripts/review-pack.mjs --task <id|auto> [--round <1|2|3>] [--include-diff] [--reset-review-slot]
node .agents/skills/dev-review/scripts/review-pack.mjs --pr <M> [--untrusted-scan] [--worktree <path>]
# 模式 B:开发者本地日常预审(支持位置目录 / --dir;--local 与 --task/--pr/--base 互斥)
node .agents/skills/dev-review/scripts/review-pack.mjs --local
node .agents/skills/dev-review/scripts/review-pack.mjs --staged
node .agents/skills/dev-review/scripts/review-pack.mjs --base <ref>注:--json 默认输出精简的 diff.hunkIndex 与统计摘要(仅传 --include-diff 时内嵌全文),防止大补丁撑爆上下文;遇冲突态(MERGE_HEAD/REBASE_HEAD)或 git diff 失败直接报错阻断。
不可信外部 PR 供应链门禁
在 .worktrees/review-pr-<M> 挂载依赖或执行任何构建/测试命令前,必须先跑静态扫描:
node .agents/skills/dev-review/scripts/review-pack.mjs --pr <M> --untrusted-scan- 扫描
base...head是否触碰.github/workflows/、package.json生命周期钩子 (preinstall/install/postinstall/prepare)、Makefile/构建脚本、.husky/、.agents/skills/、.gitattributes、依赖锁文件,或出现测试断言删除、skip/only、放宽检查。 - 命中任一高危项且未传
--human-approved-exec时,脚本输出BLOCKED_UNTRUSTED_HAZARD并以退出码3硬阻断自动执行。 - 必须先只读呈现风险给人类维护者;取得明确同意后,方可带
--human-approved-exec复跑,并在安装依赖时使用--ignore-scripts隔离。
行为/结构双门与门型评估
审查包按固定框架拆出三段评估(--json 与文本输出同步提供):
- Behavioral Gate(行为与运行时实证门):
- 验证优先级:形式验证(确定性静态检查:类型、Schema、
arch-rules、静态规则门禁)与实证验证(真实启动运行、端到端操作、界面/网页/视觉资产实际打开渲染并截图检查交互与浅深色排版、CLI/接口真实输入输出核验)优先于纯对抗式静态读代码挑刺。 - 核对
verifiedHead === HEAD与AGENTS.mdDev Profile 中的quick-test/smoke-verify/full-test/merge-gate。 - 若本次改动涉及运行态代码且配置了
smoke-verify,审查员必须在独立审查 worktree 本地运行smoke-verify并核验真实输出,严禁把未验证的运行路径转交人肉代测。 - 若
behavioralGate.empiricalVisualCheckRequired === true(变更含.tsx/.jsx/.vue/.svelte/.html/.css/.scss/.svg),必须实际打开渲染界面或视觉资产、走通核心用户交互流程并核对浅色/深色主题截图,不得仅凭静态读代码下结论。
- 验证优先级:形式验证(确定性静态检查:类型、Schema、
- Structural Gate(结构与边界门):
- 扫描 diff 新增行中的履历墓碑注释(如记录“以前是/后来改成/deprecated since”)与
借口/压制标记(
@ts-ignore、@ts-nocheck、eslint-disable、# noqa、# type: ignore、#[allow(、HACK、WORKAROUND、TEMP),要求追根因解决而非压制检查。 - 对照
AGENTS.mdarch-rules:(fromGlob -> toGlob)静态校验跨层反向引用违规。 - 对触碰超过
800行(高危1500行)的源码文件发出结构拆分预警。
- 扫描 diff 新增行中的履历墓碑注释(如记录“以前是/后来改成/deprecated since”)与
借口/压制标记(
- Door Assessment(单向门 / 双向门与爆炸半径):
doorType判为two-way(可逆代码/测试/文档改动)或one-way(弱化门禁、工作流/钩子、 发版包装/锁文件、安全/Schema 迁移、do-not-edit触碰或仓库声明merge-authority: human)。gateWeakened: true或涉及发版与不可逆边界时,mergeAuthority锁定为human-required。
代码与文档对齐核验(Doc-Code Parity)
审查包自动检测是否改动了导出 API、CLI 参数(cli-surface)、模块增删、环境要求或 high-risk: 路径,
却未同步更新 docs/TDD.md、README*.md 或 AGENTS.md;校验改动 Markdown 中的 Mermaid 16/12 防截断宽度;同时检查关联 docs/todo/(含 contributor-fork 私有隔离目录)是否存在未勾选 - [ ] 或未归档至 docs/archive/todo/,并对照 AGENTS.md「## 改哪看哪」生成 coupledSyncWarnings 与「联动同步核对(改哪看哪)」章节。流程模式下未说明的漂移列为 Must Fix 候选。
六锁防死循环收敛协议
- 实证优先与故障注入:在独立审查 worktree 运行测试;触碰高风险路径时做故障注入
(改坏一处核心判定 -> 确认测试变红 ->
git checkout -- .还原 -> 确认复绿)。形式验证与运行/渲染实证优先于静态读代码,严禁未经实证的臆测挑刺。 - 上下文隔离:只读冻结验收标准
C1..Cn、diff(含 SHA256)、门禁证据与文档对齐单,不读实施闲聊。 - 噪音过滤与三级分类:只分
Must Fix(阻塞合入)、Should Fix(建议)与Pre-existing(历史问题)。Must Fix仅限违反已冻结C*、确定性形式门禁失败、或可复现的运行/渲染/交互实证失败;主观代码风格偏好或未经实证验证的静态挑刺不得阻塞合入。Round 1 必须一次性列全同类问题全部位置。 - 轮次视野动态收窄与 Round 2+ 硬锁:Round 1 审全量
base...head并一次列全同类问题;Round 2+ 永远新建独立review子代理并在review-locks.mjs硬拦截下复审——同HEAD原地复审直接拒绝(BLOCKED_SAME_HEAD_REREVIEW,退出码2);若分支经flow.mjs sync变基,自动通过git range-diff提取!/>新侧提交限定增量视野;Round 2+ 只核前轮未关Must Fix、prevHead..HEAD增量 hunk(±3 行)及rebuts,对未改旧行或无文件无据主观新挑刺返回BLOCKED_OUT_OF_SCOPE_MUST_FIX(退出码2,非阻塞建议改用--should-fix或--pre-existing);pass前核对未清失败实证或--enforce-gates门禁(BLOCKED_PASS_WITH_OPEN_BLOCKERS)。 - 独立性与跨文件指纹硬锁:
record时--reviewer-id === implementerId直接报错SELF_REVIEW_REJECTED(退出码2);连续未决比对按完整fingerprint/(file, summary),绝不因不同文件同标C*误触发停损。 - 停损熔断与人工解锁:历史已触发停损且未解锁时,禁止通过 Round 4+
pass/changes绕过(优先返回退出码4STOP_LOSS_ESCALATE);人类拍板放行后用override解锁(支持--disposition记录四类处置统计):
node .agents/skills/dev-review/scripts/review-pack.mjs record \
[--task <id>] [--round <N>] --verdict pass|changes --reviewer-id <id> \
[--must-fix <textOrJson>...] [--should-fix <text>...] [--pre-existing <text>...] \
[--disposition "<idOrFp>:fixed|rebutted-wrong|intentional|deferred"...] \
[--rebut-accepted <idOrFp>...] [--resolved <idOrFp>...] [--enforce-gates] [--visual-checked]
node .agents/skills/dev-review/scripts/review-pack.mjs override \
[--task <id>] --human-approved --reason "<裁决理由>"说明:record 在存在关联 PR 或 linkedIssues 且处于 GitHub 在线环境时,会自动拼装规范化结构双写评论(标题统一以 审核不通过(退回)/审核通过 · Round N 开头;PR 完整审查单含四字段、对比基线、验收标准逐条核对 表、Must Fix 编号展开/Should Fix/Pre-existing 与 pf-state;Issue 摘要单含每条 Must Fix file:line 核心原因)实时双写至 PR 与关联 Issue 评论,并按裁决贴 changes-requested / reviewed 标签;403 自动降级,离线或 mcp-delegate 无直连凭据时在 githubSync.delegatedPayloads 产出各目标完整渲染正文供宿主 MCP 原样双写,同时写入 <gitCommonDir>/project-forge-govern/signals.jsonl 供 dev-govern(retro)统计误报率与下沉规则。
输出与下一跳(合入或返工闭环)
每条命令均附 [NEXT STEP] 明确提示下一合法动作:
REVIEW_PASSED:若未触发门禁弱化且未声明merge-authority: human,由当前最终通过审查的独立审查子代理直接运行node .agents/skills/dev-flow/scripts/flow.mjs merge合并 PR 并双写关闭评论(严禁自动删除分支/worktree);随后交回主会话向用户确认flow.mjs cleanup --confirm清理范围;CHANGES_REQUESTED:实施者在原impl分支追加修复(dev-flow的rework->verify->submit --rework更新同一 PR 并刷新评论),再由新的独立review子代理上下文复核;STOP_LOSS_ESCALATE(退出码4)或BLOCKED_UNTRUSTED_HAZARD(退出码3):立即停循环转交人类(override --human-approved --reason或人工批准执行)。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

