원클릭으로 Manus에서 모든 스킬 실행

reviewing-code

스타6

포크0

업데이트2026년 3월 10일 19:14

Code review checkpoint using codex review CLI. Returns structured result with pass/fail status and issues. Use when: 'code review', 'review changes', 'codex review', 'check my code'.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

GGPrompts

GGPrompts/my-plugins

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Codex Review Checkpoint

Code review checkpoint that runs codex review on the current worktree.

Note: The gate-runner script runs this automatically for issues with gate:codex-review label. This skill documents the process for manual use.

Quick Start

# Review uncommitted changes
codex review --uncommitted --title "My Review"

# Review branch changes against main
codex review --base main --title "Feature Review"

# Review a specific commit
codex review --commit abc123

What This Skill Does

Determines what to review (uncommitted changes vs branch diff)
Runs codex review (non-interactive, exits on completion)
Parses results into structured format
Writes result to checkpoint file

Workflow

Step 1: Determine Review Scope

# Check for uncommitted changes
git status --porcelain

# Check for branch diff
git diff --quiet main...HEAD && echo "No branch changes" || echo "Has branch changes"

Step 2: Run Codex Review

# For uncommitted changes
codex review --uncommitted --title "Checkpoint Review"

# For branch diff against main
codex review --base main --title "Checkpoint Review"

Codex review:

Runs non-interactively (no terminal interaction needed)
Outputs structured findings with severity levels (P1, P2, P3)
Exits with appropriate status

Step 3: Parse and Write Result

After reviewing, create a structured result:

{
  "checkpoint": "codex-review",
  "timestamp": "2026-01-19T12:00:00Z",
  "passed": true,
  "issues": [],
  "summary": "No critical issues found"
}

Result Fields:

passed: true if no P1/P2 issues found
issues: array of {severity, message, file?, line?}
summary: brief human-readable summary

Step 4: Write Checkpoint File

mkdir -p .checkpoints
cat > .checkpoints/codex-review.json << 'EOF'
{
  "checkpoint": "codex-review",
  "timestamp": "...",
  "passed": true,
  "issues": [],
  "summary": "..."
}
EOF

Decision Criteria

Pass if:

No P1 or P2 issues found
No security vulnerabilities detected
No obvious bugs or logic errors

Fail if:

P1/P2 issues found
Security issues found
Critical bugs detected

Example Output

$ codex review --uncommitted --title "Feature Review"
OpenAI Codex v0.87.0 (research preview)
--------
workdir: /home/user/project
model: gpt-5.2
...

[P2] Guard against missing script before execution — path/to/file.sh:45
  Description of the issue...

[P3] Consider adding error handling — path/to/other.ts:120
  Suggestion details...

Automated Usage

The gate-runner.sh script runs codex review automatically:

./plugins/conductor/scripts/gate-runner.sh --issue ISSUE-ID --worktree /path/to/worktree

This:

Checks issue labels for gate:codex-review
Runs codex review directly (no terminal spawn needed)
Writes checkpoint to .checkpoints/codex-review.json
Returns pass/fail status

이 저장소의 다른 Skills

같은 저장소

code-review

GGPrompts/my-plugins

Review code changes with parallel detection agents and smart fixing

2026-03-246

merge

GGPrompts/my-plugins

Branch merging and conflict resolution patterns. Use when merging feature branches, handling conflicts, or cleaning up worktrees. Trigger with "merge branch", "resolve conflicts", "cleanup worktree".

2026-03-106

automating-browser

GGPrompts/my-plugins

Controls Chrome browser: takes screenshots, clicks buttons, fills forms, downloads images, inspects pages, captures network requests, checks console errors, debugs API issues. Use when: 'screenshot', 'click', 'fill form', 'download image', 'check browser', 'look at screen', 'capture page', 'check for errors', 'debug network', 'API failing', 'console errors'. Provides MCP tool discovery for 70 tabz_* browser automation tools.

2026-03-106

brainstorming

GGPrompts/my-plugins

Brainstorm ideas and design workflows with a beads expert. Use when: 'help me plan', 'how should I structure this', 'what beads features', 'brainstorm', 'before I create tasks', 'design my workflow'. For ideation BEFORE creating issues.

2026-03-106

docs-check

GGPrompts/my-plugins

Docs/changelog checkpoint. Detects whether changes are user-facing and ensures documentation hygiene (CHANGELOG + lessons-learned) is handled or explicitly bypassed. Use when: 'docs check', 'changelog', 'release notes', 'did we update docs?'.

2026-03-106

orchestrator

GGPrompts/my-plugins

Multi-model conductor - spawns Haiku/Sonnet/Opus/Codex based on task complexity

2026-03-106

name	reviewing-code
description	Code review checkpoint using codex review CLI. Returns structured result with pass/fail status and issues. Use when: 'code review', 'review changes', 'codex review', 'check my code'.
user-invocable	true

Codex Review Checkpoint

Code review checkpoint that runs codex review on the current worktree.

Note: The gate-runner script runs this automatically for issues with gate:codex-review label. This skill documents the process for manual use.

Quick Start

# Review uncommitted changes
codex review --uncommitted --title "My Review"

# Review branch changes against main
codex review --base main --title "Feature Review"

# Review a specific commit
codex review --commit abc123

What This Skill Does

Determines what to review (uncommitted changes vs branch diff)
Runs codex review (non-interactive, exits on completion)
Parses results into structured format
Writes result to checkpoint file

Workflow

Step 1: Determine Review Scope

# Check for uncommitted changes
git status --porcelain

# Check for branch diff
git diff --quiet main...HEAD && echo "No branch changes" || echo "Has branch changes"

Step 2: Run Codex Review

# For uncommitted changes
codex review --uncommitted --title "Checkpoint Review"

# For branch diff against main
codex review --base main --title "Checkpoint Review"

Codex review:

Runs non-interactively (no terminal interaction needed)
Outputs structured findings with severity levels (P1, P2, P3)
Exits with appropriate status

Step 3: Parse and Write Result

After reviewing, create a structured result:

{
  "checkpoint": "codex-review",
  "timestamp": "2026-01-19T12:00:00Z",
  "passed": true,
  "issues": [],
  "summary": "No critical issues found"
}

Result Fields:

passed: true if no P1/P2 issues found
issues: array of {severity, message, file?, line?}
summary: brief human-readable summary

Step 4: Write Checkpoint File

mkdir -p .checkpoints
cat > .checkpoints/codex-review.json << 'EOF'
{
  "checkpoint": "codex-review",
  "timestamp": "...",
  "passed": true,
  "issues": [],
  "summary": "..."
}
EOF

Decision Criteria

Pass if:

No P1 or P2 issues found
No security vulnerabilities detected
No obvious bugs or logic errors

Fail if:

P1/P2 issues found
Security issues found
Critical bugs detected

Example Output

$ codex review --uncommitted --title "Feature Review"
OpenAI Codex v0.87.0 (research preview)
--------
workdir: /home/user/project
model: gpt-5.2
...

[P2] Guard against missing script before execution — path/to/file.sh:45
  Description of the issue...

[P3] Consider adding error handling — path/to/other.ts:120
  Suggestion details...

Automated Usage

The gate-runner.sh script runs codex review automatically:

./plugins/conductor/scripts/gate-runner.sh --issue ISSUE-ID --worktree /path/to/worktree

This:

Checks issue labels for gate:codex-review
Runs codex review directly (no terminal spawn needed)
Writes checkpoint to .checkpoints/codex-review.json
Returns pass/fail status