rrr

Automate GLM-5 code review validation and triage with glm-review.

52|12|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/dgk-dev/dgk-gpt --skill rrr-dgk-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rrr
Source: https://github.com/dgk-dev/dgk-gpt/tree/main/skills/rrr
Command: npx skills add https://github.com/dgk-dev/dgk-gpt --skill rrr-dgk-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GLM-5 코드 리뷰의 품질을 높이고, Codex가 제시한 검토를 재검증해 유효한 이슈만 정리합니다.

Core Features & Use Cases

  • GLM-5 기반 심층 코드 리뷰를 자동화하고 결과를 체계적으로 재검증합니다.
  • 변경 이력과 이슈를 정리해 팀의 품질 보증 프로세스에 바로 적용합니다.
  • Use Case: GLM-5로 리뷰를 수행하고, 자동화된 재검증으로 이슈를 확정합니다.

Quick Start

glm-review --model glm-5로 기본 리뷰를 시작합니다.

Frequently Asked Questions about rrr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GLM-5 code review and validate the findings?

To automate GLM-5 code review, you can run the glm-review command with the model set to glm-5. This initiates the review process and systematically re-verifies the findings to ensure only valid issues are output for tracking.

What is the best way to re-verify Codex code review results?

The best way to re-verify Codex code review results is by applying a secondary GLM-5 review. This validates the initial findings against the actual code, filtering out false positives and outputting only confirmed issues for your tracking system.

Can I use GLM-5 to triage code review issues automatically?

Yes, you can use GLM-5 to triage code review issues automatically. The validation process checks the detected findings against the codebase and outputs only the confirmed issues, streamlining the triage phase of your software quality assurance.

Does GLM-5 code review work for software projects upgrading their model passes?

GLM-5 code review is specifically designed for software projects upgrading to higher-model passes. It enforces the use of glm-review with the glm-5 model to perform deep code analysis and validate findings during the upgrade transition.

Why should I use a secondary AI-assisted review for issue tracking?

A secondary AI-assisted review is necessary for issue tracking to prevent false positives from entering your workflow. By validating findings against the code, it ensures that only confirmed issues are tracked, maintaining high software quality.