Trellis Review Twostage Zh
在 Trellis 子任务自检全绿、标记完成之前,做两阶段代码评审:先机械核对规范符合(对照 PRD 验收标准/决策表/禁止事项/文件清单/挂载点),再做代码质量评审(对照 .trellis/spec/guides 的工程规范与设计纪律)。用于 Codex / Claude Code 等团队协作场景,尤其当实现由 qwen3.6 35b 小模型完成时——小模型评审自己的代码不可靠,Stage 2 应升级到强模型;critical 问题阻断完成。
Install
npx skills add coldwateryi/trellis-skills --skill trellis-review-twostage-zhgit clone --depth 1 https://github.com/coldwateryi/trellis-skills.git /tmp/trellis-skills
mkdir -p ~/.claude/skills
cp -r /tmp/trellis-skills/trellis-review-twostage-zh ~/.claude/skills/trellis-review-twostage-zhPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Trellis 双阶段评审 ## 概览 子任务实现自检全绿后、标记完成前的质量门。分两段独立评审: - **Stage 1 规范符合**:对照 `prd.md` 机械核对,可由小模型 + 检查清单完成。 - **Stage 2 代码质量**:对照工程规范与设计纪律,**应由强模型**完成(小模型评审自己产出不可靠)。 任一阶段发现 **critical** 问题即阻断,打回 `trellis-implement-tdd-zh` 修复;修复后重新评审。 触发:`trellis-implement-tdd-zh` 收尾自检全绿、交接评审时。 每次评审都写入任务目录下固定的 `<task-dir>/review-report.md`。第一次评审时从 `references/review-report-template.md` 创建,后续重审在同一个文件里追加新的 review round 块;不要改 skill 目录里的模板文件。 ## 约束 - **评审基于 diff + `prd.md`**,不重读整个需求文档。 - **Stage 1 与 Stage 2 分开做,不合并**——合并会让"是否照规范实现"和"代码好不好"互相掩盖。 - **Stage 2 用强模型**(角色分层模型分配)。若只有小模型可用,Stage 2 至少严格走 `references/review-stage2-checklist.md` 逐项核对,并在报告里标注"未经强模型评审"风险。 - **按严重度分级**:critical(阻断)/ major(应修)/ minor(可记录后续)。只有 critical 阻断完成。 - 评审者**不直接改代码**:产出问题清单交回实现技能修,保持"写"与"审"分离。 ## 工作流 ### 1. 准备 - 取本任务 diff(相对任务起点)。 - 读 `prd.md`:`验收标准`、`决策表`、`禁止事项`、`文件清单`、`行为约束`;若有 `design.md` 读`挂载点清单`、`编排-计算分离`。 - 若有 `check.jsonl`:预加载其中的回归/风险上下文。 ### 2. Stage 1 · 规范符合(机械核对,可小模型) 逐项走 `references/review-stage1-checklist.md`,核对实现是否**照规划做了**: - 每条 `AC-xxx` 是否有对应测试且为绿? - 改动文件是否都在「文件清单」内?有无清单外文件被改? - 是否违反任何「禁止事项」(新建已有基类、引入未列依赖等)? - 「决策表」的选择是否被遵守(注解 / 命名 / schema / 分支)? - 「挂载点清单」是否逐项接线(路由 / 配置 / 订阅 / DI)? - 任一不符 → 记为 issue。AC 无测试、改了禁止改的文件、挂载点漏接 = **critical**。 ### 3. Stage 2 · 代码质量(强模型) 逐项走 `references/review-stage2-checklist.md`,对照 `.trellis/spec/guides/` 与设计纪律评审**代码本身**: - **编排-计算分离**:编排逻辑与计算逻辑是否混在一处?纯计算是否被塞进编排层导致难测? - **结构健康度**:是否往本就偏胖的文件继续堆?是否制造了"什么都装的筐"? - **简化/复用**:有无重复实现已有能力?有无未被要求的过度抽象(违反 YAGNI)?
Details
- Skill name
trellis-review-twostage-zh- Repository
- coldwateryi/trellis-skills
- Path
trellis-review-twostage-zh/SKILL.md- License
- MIT
- Repo updated
- 3 July 2026
FAQ
What does the Trellis Review Twostage Zh skill do?
在 Trellis 子任务自检全绿、标记完成之前,做两阶段代码评审:先机械核对规范符合(对照 PRD 验收标准/决策表/禁止事项/文件清单/挂载点),再做代码质量评审(对照 .trellis/spec/guides 的工程规范与设计纪律)。用于 Codex / Claude Code 等团队协作场景,尤其当实现由 qwen3.6 35b 小模型完成时——小模型评审自己的代码不可靠,Stage 2 应升级到强模型;critical 问题阻断完成。
How do I install the Trellis Review Twostage Zh skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add coldwateryi/trellis-skills --skill trellis-review-twostage-zh. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Trellis Review Twostage Zh popular?
It lives in coldwateryi/trellis-skills, which has 44 GitHub stars and 1 forks.
Related skills
Trellis Debug Systematic
44coldwateryi/trellis-skills
When a test should be green but stays red, or a self-check command fails during Trellis subtask implementation/verification, use this non-deviable rigid script for systematic root-cause pinpointing and minimal fix. Used when Codex / Claude Code drives a small-parameter model like qwen3.6 35b—small models quickly spiral out of control when debugging freely; this skill uses "one change at a time, must re-run after change, no guessing" iron rules to lock it on a narrow path with defensive regression checks.
Trellis Debug Systematic Zh
44coldwateryi/trellis-skills
当 Trellis 子任务实现/验证过程中测试该绿不绿、或自检命令失败时,用一段不可偏离的刚性脚本做系统化根因定位与最小修复。用于 Codex / Claude Code 等驱动 qwen3.6 35b 这类小参数模型调试时——小模型一旦自由发挥就会到处乱改,本技能用"一次只改一处、改完必重跑、禁止猜"的铁律把它锁在窄路径上,并带防御性回归检查。
Trellis Delivery Controller
44coldwateryi/trellis-skills
Trellis requirements-to-delivery entrypoint and workflow controller. Use when the user wants to invoke one Trellis skill that detects the current stage and routes work across requirements analysis, MVP task planning, post-MVP gap audit, delivery loop, TDD implementation, systematic debugging, two-stage review, and final acceptance. Coordinates trellis-zero-to-mvp, trellis-mvp-to-delivery, trellis-implement-tdd, trellis-debug-systematic, and trellis-review-twostage while enforcing safety gates.
Trellis Zero to Mvp Zh
44coldwateryi/trellis-skills
从完整需求文档创建 Trellis MVP 任务树。用于 Codex 收到产品说明、需求文档、PRD、从 0 到 MVP 的新项目需求、大型能力建设请求,或已经手工实现了一部分功能的项目时,先做只读分析,分配稳定 REQ/AC 编号,生成需求追踪矩阵和项目契约,识别已有实现证据,通过渐进式批次规划和子代理协作形成完整 MVP 父子任务树、PRD、设计/实现产物计划,并在用户确认后创建 Trellis 任务;不编写应用代码。
Launch Gate
43rohitg00/agentbrain
Use when a launch needs a go/no-go decision with rollback and monitoring evidence.
Session Team
44jiahao-shao1/sjh-skills
Run a team in T3 Code - a sync thread the user talks to, an ops leader thread that dispatches, checks in and reports only by writing the team doc, and workers the leader runs as delegated subagents - coordinated through that doc, typed reports and scheduled check-ins. Triggers include 'be the leader', 'ops leader', 'leader session', 'start a team of sessions', 'split this across sessions', 'coordinate sessions', 'sync-with-me', '当 leader', '开个 leader', '开个 ops leader', '开几个 session', '拆给几个 session', '多 session 协作', '让 session 之间协作'. Needs the T3 Code thread and delegation tools. Not for a sing
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.