review
CTK risk-based review of current changes: picks reviewer depth by diff risk. For 'review my changes'.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- review
- description
- CTK risk-based review of current changes: picks reviewer depth by diff risk. For 'review my changes'.
- argument-hint
- [spec path or ticket]
02 资源文件 2
- 参考文档references/checklist.md767 B
- 参考文档references/risk.md907 B
03 SKILL.md 正文
Review the current change against $ARGUMENTS (spec or ticket; if empty, infer from the task).
1. Scope
Get the change with git diff (or git diff <base>..HEAD). Write it to a scratch file;
reviewers receive that path, never pasted diff text.
2. Classify risk from the diff
High if it touches any of: auth, money, data migration, concurrency, public API, security, secrets.
Medium if it changes behavior across modules or adds a dependency. Otherwise low.
Criteria and examples: references/risk.md.
3. Review by risk
- Low: run the self-review checklist in
references/checklist.md. No subagent. - Medium: spawn
ctk:reviewer. - High: spawn
ctk:high-risk-reviewer. Hand the reviewer: diff file path, spec path, base sha. Spawn is confirmed only with an agent id; if refused (TEAM_CAPACITY_REACHED), run the checklist yourself and say so.
4. Two axes
- Standards: project rules (CLAUDE.md), correctness, simplicity.
- Spec: does the change do what the ticket says; anything missing or extra.
5. Findings
Each finding: path:line, the failing scenario, one-line fix. Drop anything a linter or formatter owns.
Verify each finding against the code before reporting it. Report: risk level, reviewer used, findings or
"none found" with what was checked. Do not fix in this skill unless asked. In a team the lead only routes: SendMessage findings on a
teammate's slice to its live implementer (one fix round, then re-review); the lead does not fix them itself.
04 同仓库更多 Skills
team
Invoke before spawning several agents, or when asked to use CTK, a team or parallel work (多個 Agent, 平行, ctk 流程). Keeps the worker cap.
debug
CTK debug for failing tests or behavior: reproduce, diagnose, fix, regression. Use when CTK debugging is requested, or when no standalone debugging skill is installed.
ctk
CTK: team progress, 5h/weekly usage, worker cap and settings, profile sync across machines.
graders
暂无简介
graders
暂无简介
graders
暂无简介