메뉴
peer-review a plan, design, or implementation, find the one critical risk, list other gaps, propose a fix for the critical risk, and update the plan. Triggers: peer review a plan, review an implementation, assess a design, check a proposal for gaps.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | peer-review |
| description | peer-review a plan, design, or implementation, find the one critical risk, list other gaps, propose a fix for the critical risk, and update the plan. Triggers: peer review a plan, review an implementation, assess a design, check a proposal for gaps. |
Read everything relevant before analyzing:
package.json/requirements.txt/Cargo.toml for related libsCompare the plan to the requirements. Check completeness, edge cases (boundaries, empty inputs, max values, races), error states and rollback, failure modes (a downstream service down/slow/returning garbage), hidden ordering or version conflicts, performance (N+1, unbounded loops, leaks), security (input validation, auth, secrets, data integrity), and test adequacy.
Focus on what is most likely to cause failure, not every theoretical issue.
Exactly four sections. Maximum clarity, minimum words.
One paragraph naming the single thing most likely to cause failure, why it is dangerous and under what conditions it breaks. Pick the highest-impact, most probable one; do not list several.
Bulleted secondary issues, one line each, formatted - <issue> → <impact>. Only
real, material issues, no nitpicks or theoretical concerns.
Numbered, concrete, actionable steps that address the critical risk only.
One sentence, exactly one of: "Ship it." / "Fix the critical risk first, then ship." / "Needs rework." No explanation.
Apply the Fix steps to the plan files directly, the smallest change that mitigates the critical risk. Report which files changed and the fix applied.
box a git repo, clone it locally and search the real source, with a tracked manifest. Delegates repo work to subagents when available, runs in the main thread otherwise. Triggers: a VCS URL (GitHub, GitLab, Bitbucket), a previously cloned repo name, or a request to clone/search/explore a repo. Flags: --persist, --update, --list, --no-subagents.
explain-diff: explain a code change, diff, branch, or PR as a rich self-contained HTML page. Flags: --target <branch>, --pr <n>, --staged, --unstaged, --output <path>.
fix a Linear ticket end to end: fetch it, branch, classify mode, plan, implement, review. Flags: --base <branch> (default main), --mode <mode> (default auto; values: auto, scratch, modify, debug, trivial), and a ticket ID positional arg.
fix PR review feedback: fetch unresolved threads, triage each finding skeptically, fix what holds, reply on threads, commit and push. Triggers: /fix-pr, address PR reviews. Reached by prath-mode after make-pr. Flags: --pr <n|url>, --no-push, --no-reply.
notify the user via Discord webhook embed. Triggers: /notify, send a Discord notification, alert me when done, ping me on Discord. Flags: --task, --link, --webhook, --color, --field, --content, --dry-run.
Route a task to the right skill in prathamdby/skills and run multi-step workflow chains. Verifies the leaf skill is installed before invoking it.