code-reviewer

Review code diffs and implementation evidence in Korean via Codex.

Updated Jun 7, 2026
One-click install
npx skills add https://github.com/lukasdeveloperacc/PersonalAgentPlugins --skill code-reviewer-lukasdeveloperacc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/lukasdeveloperacc/PersonalAgentPlugins/tree/main/codex/plugins/socrates-codex-partner-plugin/skills/code-reviewer
Command: npx skills add https://github.com/lukasdeveloperacc/PersonalAgentPlugins --skill code-reviewer-lukasdeveloperacc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Codex, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the code review process by providing a Korean-first Codex implementation critique lane, enabling efficient review of diffs and implementation evidence in a persistent cmux pane.

Core Features & Use Cases

  • Korean-first Review: Offers code reviews in Korean, catering to Korean-speaking users.
  • Persistent Pane: Utilizes a persistent cmux pane for continuous review sessions.
  • Read-only by Default: Ensures a safe, non-intrusive review environment.
  • Verdict File Generation: Switches to harness-reviewer for file-authoritative STOP/GO verdicts.
  • Use Case: Ideal for teams that require a detailed code review process with a focus on Korean documentation and implementation evidence.

Quick Start

Run the 'code-reviewer' skill to initiate a code review session in a persistent cmux pane.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I get a code review in Korean for my diffs?

Korean code review is generated by analyzing diffs and implementation evidence using Codex, outputting the critique directly in a persistent cmux pane for continuous sessions.

Do I need Codex to run the Korean code review process?

Codex is required for code analysis and review, as the Korean-first implementation critique depends on it to evaluate diffs and generate implementation evidence feedback.

What is the best way to review implementation evidence safely?

Implementation evidence review operates read-only by default in a persistent cmux pane, ensuring a safe, non-intrusive code analysis environment for evaluating diffs.

Can I generate a STOP or GO verdict file after a code review?

File-authoritative STOP or GO verdicts are generated by switching to the harness-reviewer component, which provides the final authoritative decision following the review session.

How does Korean-first code review work in a persistent pane?

Korean-first code review works by running Codex analysis within a persistent cmux pane, allowing users to maintain continuous, read-only review sessions focused on Korean documentation.