code-reviewer

Analyze code changes against AGENTS.md rules and write a .codex-reviewed stamp.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/JayJihyunKim/rein --skill code-reviewer-jayjihyunkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/JayJihyunKim/rein/tree/main/plugins/rein-core/skills/code-reviewer
Command: npx skills add https://github.com/JayJihyunKim/rein --skill code-reviewer-jayjihyunkim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a Rein-native fallback reviewer that analyzes changed code against AGENTS.md rules and generates a review stamp when the primary codex-review gate fails.

Core Features & Use Cases

  • Fallback code-review path for failed or unavailable codex-review.
  • Applies AGENTS.md rules plus a checklist to audit modified files and generate a stamp.
  • Enables an auditable trail of review decisions for governance and compliance.
  • Integrates with trail/dod/.codex-reviewed stamping to record outcome and reasoning.

Quick Start

Trigger the fallback review by simulating codex-review failure and let the plugin generate the stamp.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I run a fallback code review when the primary codex-review gate fails?

Trigger the fallback code review by simulating a codex-review failure; the plugin then loads AGENTS.md rules, executes a checklist on changed files, and writes the review stamp automatically.

What is an audit trail for code review decisions and how does stamping work?

Review stamping records governance decisions by writing fields like reviewer, timestamp, fallback_reason, files_reviewed, and review_round into the trail/dod/.codex-reviewed file for compliance tracking.

How do I apply AGENTS.md rules to audit modified files in a Rein-native workflow?

Load AGENTS.md rules and execute a structured checklist against modified files to count reviewed files and produce a plan-driven gate result for code changes.

Do I need a primary codex-review gate configured to use a fallback reviewer?

The fallback reviewer activates only when the primary codex-review gate times out or exits non-zero, ensuring an auditable review path when the standard gate is unavailable.

What limitations exist when relying on a fallback code-review guardrail for compliance?

The fallback guardrail is limited to secondary activation upon primary codex-review failure, serving as a compliance backup rather than a standalone replacement for the standard review gate.