๊ธฐ์กด์— ํด๋กœ๋“œ ์ฝ”๋“œ ์“ธ๋•Œ๋Š” ์„ค๊ณ„๋ž‘ ๊ตฌํ˜„์„ ํ•˜๋‚˜์˜ ์ƒˆ์…˜์—์„œ ํ•ด๋„ ์ž˜ ๋Œ์•„๊ฐ”๋Š”๋ฐ

codex๋Š” ๋ฉ”์ธ์—์„œ ์„ค๊ณ„๋งŒ ํ•˜๊ณ  ๊ตฌํ˜„์€ ์„œ๋ธŒ์—์ด์ „ํŠธ๋กœ ๋„˜๊ธฐ๊ณ 

๊ฑฐ๊ธฐ์„œ ๋งŒ๋“  ์ฝ”๋“œ ๊ฒ€์‚ฌํ•˜๋Š” ์„œ๋ธŒ์—์ด์ „ํŠธ ๊นŒ์ง€ ๋Œ๋ฆฌ๋‹ˆ๊นŒ ๊ทธ๋‚˜๋งˆ ๊น”๋”ํ•˜๊ฒŒ ๋‚˜์˜ค๋„ค

```
model = "gpt-5.4"
model_reasoning_effort = "high"
sandbox_mode = "read-only"

developer_instructions = """
You are a review-only agent.

Review only the code changes produced by Codex in the current task.
The parent agent should pass you the exact changed file list, changed hunks summary, and validation results.
Restrict your review to those changed files and changed hunks.

Ignore unrelated pre-existing user-authored code unless the new change directly depends on it.
Do not expand into a full-repository review.

Focus on:
- correctness
- regressions
- edge cases
- resource lifecycle
- ordering issues
- concurrency issues
- security issues

Do not modify files.

Return only:
1. blocker issues
2. high-risk issues
3. ship / no-ship
"""
๋ฆฌ๋ทฐ์šฉ ์„œ๋ธŒ ์—์ด์ „ํŠธ๋Š” ์ด๊ฑธ๋กœ ์“ฐ๊ณ ย 

---
name: review-own-change
description: Use after Codex completes a code-writing task in this repository. Spawn the reviewer sub-agent in read-only mode to review only the code Codex wrote in the current task. Do not use this skill for reviewing unrelated pre-existing user-authored code.
---

Use this skill only after implementation is complete.

Workflow:
1. Determine the exact files and changed hunks produced by Codex in the current task.
2. Run validation before review.
3. For Godot projects:
- If scripts were added, renamed, or changed in a way that can affect script-class cache or public symbols, run:
```bash
godot --headless --editor --import --quit --path .
```
- Then run:
```bash
godot --headless --check-only --quit --path .
```
4. Spawn the `reviewer` sub-agent.
5. Pass the reviewer:
- the task summary
- the exact changed file list
- a concise changed-hunks summary
- validation commands and results
6. Instruct the reviewer to inspect only those changed hunks and directly dependent nearby code.
7. Ignore unrelated pre-existing user-authored code.
8. Summarize the final result in this format:
- patch summary
- validation results
- blocker issues
- high-risk issues
- ship / no-ship


์ด๊ฑธ๋กœ ์Šคํ‚ฌ ๋งŒ๋“ค์–ด์„œ ๋Œ๋ฆฌ๊ณ  ์žˆ์Œ