메뉴
Review new/changed code for bugs. TRIGGER when: checking for bugs, auditing new logic, or validating correctness (e.g., "any bugs here?", "check this for bugs", "is this correct?").
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | bug-dog |
| description | Review new/changed code for bugs. TRIGGER when: checking for bugs, auditing new logic, or validating correctness (e.g., "any bugs here?", "check this for bugs", "is this correct?"). |
Review new/changed code for bugs.
Important:
Step 1 — Read the diff. For each meaningful change, describe what is the new/changed behavior.
Step 2 — Stress-test. For each new/changed behavior, ask: does this make sense? Does it miss edge cases? Does it handle sad paths? Look for: logic errors, off-by-one errors, null/undefined gaps, missing edge cases, race conditions, incorrect assumptions, wrong operator, swapped arguments, resource leaks, short-circuit mistakes, boundary conditions, silent data loss, and incorrect error propagation.
Output format:
Scope (pass as arguments):
main: review all commits since the last merge from mainHEAD~3: review the last 3 commitsabc123..HEAD, main..HEAD)Orchestrate the review skills (review-dog, regression-dog) into one deduplicated, adjudicated report. TRIGGER when: the user wants a combined/full/aggregated review of a branch or commit (e.g., "run the full review", "review this branch with everything", "give me the aggregated review").
Review code changes for bugs, style, best practices, and adherence to project conventions.
Review code for regressions. TRIGGER when: reviewing changes, checking for breakage, or auditing commits (e.g., "did I break anything", "review last commit").
Add JSDoc to code entities. TRIGGER when: user asks to add/write/improve JSDoc (e.g., "add jsdoc to Foo", "jsdoc for Bar").