review
Review a local change, branch, pull request, or stack for correctness, regressions, security, tests, and unnecessary complexity. Use when asked to review rather than implement.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-29
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- review
- description
- Review a local change, branch, pull request, or stack for correctness, regressions, security, tests, and unnecessary complexity. Use when asked to review rather than implement.
02 资源文件 26
- 参考文档docs/acceptance.md5.0 KB
- 参考文档docs/quickstart.md4.1 KB
- 参考文档scaffold/root/README.md2.8 KB
- 参考文档scaffold/rules/内容单元关系规则.md697 B
- 参考文档scaffold/rules/内容单元去重与版本规则.md574 B
- 参考文档scaffold/rules/内容单元字段规范.md907 B
- 参考文档scaffold/rules/处理流程.md698 B
- 参考文档scaffold/rules/新增文稿进入系统流程.md1.1 KB
- 参考文档scaffold/rules/来源命名规范.md543 B
- 参考文档templates/主题地图模板.md265 B
- 参考文档templates/方案单元模板.md471 B
- 参考文档templates/案例单元模板.md449 B
- 参考文档templates/概念单元模板.md412 B
- 参考文档templates/观点单元模板.md431 B
- 参考文档templates/选题装配模板.md437 B
- 参考文档templates/问题单元模板.md462 B
- 脚本tools/assemble-topic-from-units.js24.2 KB
- 脚本tools/extract-sample-units.js104.9 KB
- 脚本tools/fill-obsidian-links.js4.5 KB
- 脚本tools/generate-duplicate-candidates.js16.4 KB
- 脚本tools/generate-link-map.js6.1 KB
- 脚本tools/generate-source-registry.js4.6 KB
- 脚本tools/generate-unit-draft.js2.2 KB
- 脚本tools/init-content-system.js3.9 KB
- 脚本tools/rebuild-processing-ledger.js2.9 KB
- 脚本tools/summarize-system.js1.8 KB
03 SKILL.md 正文
Review
Establish scope
Resolve the requested target before reading code: current working tree, branch, pull request, or stack. Prefer the smallest faithful diff. For a PR, inspect its description, changed files, and relevant base; for a stack, review each PR against its immediate parent as well as the complete stack when cross-PR interactions matter.
Do not modify the target unless the user explicitly asks for fixes. Do not review untrusted or sensitive files outside the agreed scope.
Review method
- Read the surrounding contract and callers for each non-trivial change.
- Check correctness, error paths, ownership/lifecycle, concurrency, security and privacy boundaries, API compatibility, and test coverage.
- Verify claims with targeted commands where possible. A passing test suite does not replace reasoning about untested paths.
- Report only actionable findings introduced by the target. Do not raise pre-existing issues unless they obstruct a correct assessment.
Use independent review passes only when they add distinct expertise; consolidate duplicates before reporting. Never claim a tool call or reviewer happened without its observable result.
Finding quality
Each finding must include severity, file and line, the failure condition, and a short explanation of the consequence. Severity is about impact and likelihood:
bug: a likely correctness, reliability, security, or compatibility defect.suggestion: an improvement with a concrete maintenance or clarity benefit.nit: cosmetic; omit unless the user requested exhaustive feedback.
Prefer a few high-confidence findings to speculative lists. If there are none, say so and name residual risks or checks not run.
Output
Lead with the findings, ordered by severity. Then give a concise scope, evidence, and any verification performed or unavailable. For a stack, retain the PR association for every finding. Do not include generated command dumps, reviewer prompts, or internal orchestration logs in the user-facing report.
04 同仓库更多 Skills
train
Launch a new max_llm training run on both GPUs (RTX 4090 + RTX 3090 Ti) through torchrun DDP, resolving the TOML config by name or path. Use only when the user explicitly asks to start, launch or begin a run — "resume", "continue" or "keep training" mean the existing run; takes an optional config name or path.
serve-live
Before a person looks at a running service, make sure what is running IS the code in the checkout. Restart the services your change actually touched — not every service — and verify each is serving the current commit rather than merely answering; check the remaining dependencies are up without bouncing them. Use whenever you finish work a person will view in a browser or client, whenever you say a page or service is ready, after any commit that changes served code, and when asked to 'restart', 'refresh the services', 'is it live', or 'serve the latest'. Also covers waiting for lazy warm-up before calling a service ready.
review
Review a local change, branch, pull request, or stack for correctness, regressions, security, tests, and unnecessary complexity. Use when asked to review rather than implement.
regression-coverage
Reshape a slow or brittle test suite around observable user journeys and published contracts. Use when pruning tests, repairing weak smoke coverage, or addressing repeated feature regressions.
pr-babysit
Monitor selected pull requests and report or safely act on review, CI, mergeability, and stack state.
keel
Use a project's local keel code graph to assess change impact, find callers and reuse candidates, validate a plan, or check an edit. Applies only in a repository with a .keel/ directory; skip it for prose-only work.