Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/yamadashy/skills --skill codex-review-loop명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Consult OpenAI Codex as an advisor via `codex exec` — a cross-model second opinion on a hard design decision, a stuck debugging session, or a close review call. A consultation, not an implementation hand-off. Triggers on: 'consult codex', 'ask codex for advice', 'get codex's opinion', 'second opinion from codex', or when a judgment call is too close to make alone.
Consult Fable (claude-fable-5, the tier above Opus) as an advisor — a second opinion on a hard design decision, a stuck debugging session, or a close review call. From Claude Code, spawn a subagent on model fable; from any other harness, call the Claude Code CLI. A consultation, not an implementation hand-off. Triggers on: 'consult fable', 'ask fable', 'get fable's opinion', 'second opinion from fable', or when a judgment call is too close to make alone.
Shape what a message says around the recipient's state rather than the sender's. Corrects the measured sender biases first (underestimating that people say yes, overestimating how well you were understood, arguing from your own values), then channel and friction, then barriers to comprehension, and wording last. Load-bearing claims carry an evidence grade, and popular techniques that the evidence does not support — or that fail an honesty test — are named and excluded. Use when drafting or revising a spoken or written request, proposal, explanation, bad news, apology, or a reply in a disagreement — and on "make this more persuasive", "how should I phrase this", "they'll say no", "this didn't land". Changes substance and stance — not layout, not scannability, not prose rhythm.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | codex-review-loop |
| description | Iterative codex review-and-fix loop |
Repeat the following cycle on the current branch's changes against main (max 3 iterations):
npm run lint and npm run test. Fix any regressions and repeat this step until all checks pass before continuing.Stop when no "Fix" items remain or 3 iterations are reached. Print a summary of what was fixed and what was skipped.