| name | rr |
| description | 코드 리뷰. 작업 후 변경사항을 Z.AI 모델로 검토하고, Codex가 결과를 다시 검증해 유효한 이슈만 정리한다. /rr 또는 'GLM 리뷰' 요청 시 사용. |
/rr
Use glm-review as a second reviewer for the current change set, then validate the reported issues against the actual code before you trust or repeat them.
Default Flow
- Determine the exact change scope first.
- If the user points to a commit, prefer commit mode.
- If the user says
staged, use staged mode.
- If the user says
pr, use PR mode.
- If the workspace has mixed unrelated changes, build a focused diff file for only the intended files.
- Run a quick connectivity check only when the environment looks suspect:
glm-review --health
- Run the review with the narrowest correct input:
glm-review
glm-review --mode staged
glm-review --mode pr
glm-review --mode commit --ref <COMMIT_HASH>
glm-review --diff-file /tmp/glm-review-diff.patch
- Treat the output as a candidate issue list, not ground truth.
- Re-open the referenced code and verify each claim.
- Report only valid issues, ordered by severity.
- If fixing issues is in scope, fix them and rerun the closest relevant verification.
Choosing Review Input
Prefer the most specific path that isolates the current task:
glm-review --mode commit --ref <COMMIT_HASH>
- committed subset of files:
glm-review --mode commit --ref <COMMIT_HASH> --files src/a.ts src/b.ts
