Menu
Use when auditing a retikz module or subsystem read-only to find beta cleanup, refactor, correctness, schema, test, or docs consistency findings before deciding which items become roadmap TODOs.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use when changing any retikz apps/docs content, route data, i18n, demo, SourceLinks, or schema reference before loading the matching page-type skill.
Use when retikz needs multiple independent LLMs to review the same fixed code, ADR, implementation plan, test contract, commit, or working-tree snapshot before a gate or delivery decision.
Use when an Alpha ADR needs a pre-implementation capability gate, or a Beta milestone needs code-based completeness and package-boundary auditing.
Use when planning a retikz architecture direction, version roadmap, or alpha feature that may need a long-lived ADR before implementation.
Use when retikz work is primarily refactoring, reorganization, renaming cleanup, modularization, or internal simplification and should start from a reviewed implementation plan before code changes.
Use when retikz implementation, adversarial testing, and docs are complete, and an ADR or beta TODO needs changelog, contract consistency review, roadmap status updates, or final human acknowledgement.
| name | develop-review |
| description | Use when auditing a retikz module or subsystem read-only to find beta cleanup, refactor, correctness, schema, test, or docs consistency findings before deciding which items become roadmap TODOs. |
对一个 workspace 包或子系统做横向通读，输出可 triage 的分级报告。本 skill 只发现问题，不改产品代码、不改 roadmap、不提交。
| 场景 | 用哪个 skill |
|---|---|
| 横向审一个模块，找 beta TODO 候选 | develop-review |
| 审计已有测试是否过期、重复或临时 | test-review |
| 固定 commit / PR / diff 多模型评审 | cross-review |
| 为疑似 bug 写测试坐实 | cross-test |
| 已登记 TODO 要修 | flow-beta |
| 新功能 / 新 IR / 新公开字段 | flow-alpha / develop-design |
@retikz/core）或子系统 / 路径集。git rev-parse HEAD
git status --short
AGENTS.md。standard-structure 分流读取对应 standard-* skill。apps/docs/AGENTS.md 和必要 docs skill。每条 finding 必须有代码位置和成因，不能只写“可以优化”。
as any / ignore / 非必要断言、测试覆盖。若审查目标是测试资产本身是否过期、重复或临时，转用 test-review，不要在本 skill 中混合展开。.describe 完整与质量、const object enum、非法状态不可表达、同名同义。预估 Level 按修复方案触及范围写：internal / visible / breaking，与严重度独立。
写入：
notes/reports/develop-review-YYYY-MM-DD-<module>.md
该目录被 .gitignore 忽略，报告不 stage、不 commit。
报告结构：
# Develop Review Report: <module>
日期：
审查范围：
基准快照：
所属分组 / 版本通道：
覆盖率声明：
## 结论概览
## BLOCKING
| # | 位置 | 维度 | 问题 | 建议改法 | 预估 Level | 坐实出口 |
## WARNING
| # | 位置 | 维度 | 观察 | 建议改法 | 预估 Level | 坐实出口 |
## INFO
| # | 位置 | 维度 | 观察 |
## 横向发现
## 建议 triage
无某档时写“无”。
git status --short 与基线相比，除 ignored 报告外没有产品文件变化。