Menú
코드 리뷰. 작업 후 변경사항을 Z.AI 모델로 검토하고, Codex가 결과를 다시 검증해 유효한 이슈만 정리한다. /rr 또는 'GLM 리뷰' 요청 시 사용.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Persistent verification mode. Use when the user explicitly says `/test` or clearly wants exhaustive test, QA, and fix loops before signoff, especially when they want you to keep grinding while they are away. Bias Codex toward running the relevant existing test stack, browser or desktop verification, and diagnosis repeatedly until the requested surface is verified or a real blocker remains.
GLM-5 코드 리뷰. /rr의 상위 버전으로 더 강한 모델로 변경사항을 검토하고, Codex가 결과를 다시 검증해 유효한 이슈만 정리한다.
Local verify-commit-push wrapper for Codex. Use only when the user explicitly says `/cp` or clearly asks to finish the current work by running the relevant local checks, staging intended files explicitly, committing on the current branch, and pushing. This workflow may commit directly to `main` or `master` when that is the repo's chosen operating model.
Frontend design mode for strong visual direction, UI polish, redesigns, landing pages, and production-grade interface work, including shadcn-based surfaces. Use when the user says `/fd` or explicitly asks for better design, styling, layout, visual quality, or UX polish.
Persistent completion mode. Use when the user explicitly says `/ralph` or clearly wants you to keep iterating until the task is actually finished, repeating implement-verify-fix loops instead of stopping at partial progress.
Explicit extra-research mode. Use only when the user says `/re` or clearly asks for a research-heavy pass before coding. This skill should bias Codex toward more source-checking and justification without replacing its normal orchestration.
Basado en la clasificación ocupacional SOC
| name | rr |
| description | 코드 리뷰. 작업 후 변경사항을 Z.AI 모델로 검토하고, Codex가 결과를 다시 검증해 유효한 이슈만 정리한다. /rr 또는 'GLM 리뷰' 요청 시 사용. |
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.
staged, use staged mode.pr, use PR mode.glm-review --health
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
Prefer the most specific path that isolates the current task:
glm-review --mode commit --ref <COMMIT_HASH>
glm-review --mode commit --ref <COMMIT_HASH> --files src/a.ts src/b.ts
GIT_ROOT=$(git rev-parse --show-toplevel)
cd "$GIT_ROOT" && git diff HEAD -- <file1> <file2> ... > /tmp/glm-review-diff.patch
glm-review --diff-file /tmp/glm-review-diff.patch
If the diff is empty, stop and say there is nothing to review.
glm-review output without checking the code.Common fixes:
command not found: glm-review
Install it with npm install -g glm-reviewZAI_API_KEY not set
Export ZAI_API_KEY in the shell or your normal secret-loading path before rerunning401 or auth failure
Re-run glm-review --health after refreshing credentialsReturn: