메뉴
Fetch and address inline PR review comments on the current GitHub pull request by reading the affected files, applying targeted fixes, following project conventions, and summarizing resolved and unresolved items.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use this skill whenever possible for structural code search before using grep/rigrep or similar plain text search. apply when locating functions, calls, imports, JSX, decorators, error handling, unsafe APIs, duplicated expressions, refactor targets, or any code pattern where syntax-aware matching is more reliable than text matching.
Expert Elixir assistant for writing, reviewing, debugging, and refactoring idiomatic Elixir, Phoenix, LiveView, Ecto, OTP, and ExUnit code. Use whenever the user asks to create, modify, review, explain, modernize, or test Elixir code, including modules, contexts, schemas, migrations, LiveViews, GenServers, supervisors, tests, docs, and typespecs. Enforces project-local conventions, mix format, official naming conventions, official Elixir anti-pattern guidance, and practical idiomatic style.
Expert Python assistant for writing, reviewing, and refactoring idiomatic, modern Python (3.12+) code. Use for any task that introduces or changes Python code. Enforces PEP 8, PEP 257, and PEP 484/585/604/695 typing conventions across formatting, naming, imports, docs, typespecs, error handling, classes, dataclasses, and collections, while avoiding common anti-patterns. Web (FastAPI/Django), async, and packaging specifics live in references/web-async-packaging.md (loaded on demand). Use for: any new or modified Python code, modules, classes, dataclasses, type hints, async code, tests, docs, and code review/refactoring. Do not use for: non-Python code, infra unrelated to Python, or pure architecture with no Python code.
Expert Elixir + Phoenix LiveView PR reviewer with deep context gathering and git/gh CLI workflow. Use whenever you want a rigorous review of an Elixir/Phoenix (especially LiveView) pull request, including behavior changes, security and multi-tenant data isolation (cross-customer/IDOR risks), dead-code cleanup, migration safety, and LiveView lifecycle issues — even if the user just says "review this PR" or "look at this diff".
Review Python pull requests for behavioral bugs, security risks, and regression risk using git diff and optional gh PR context. Use for backend/API Python PR reviews; avoid for non-Python repos or style-only lint passes.
Fetch and address inline PR review comments on the current GitHub pull request in Elixir/Phoenix projects by reading the affected files, applying targeted fixes following Elixir and project conventions, and summarizing resolved and unresolved items.
| name | address-review |
| description | Fetch and address inline PR review comments on the current GitHub pull request by reading the affected files, applying targeted fixes, following project conventions, and summarizing resolved and unresolved items. |
Fetch all inline comments from the current PR, inspect the affected files, and apply each fix carefully and minimally.
Resolve actionable inline PR review comments while preserving existing behavior, following project conventions, and avoiding unrelated changes.
gh pr view --json number,headRefName
PR=$(gh pr view --json number --jq .number)
REPO=$(gh repo view --json nameWithOwner --jq .nameWithOwner)
gh api "repos/$REPO/pulls/$PR/comments" \
--jq '[.[] | {path: .path, line: .line, body: .body}]'
Collect all inline comments, ignore comments that are clearly outdated or no longer applicable, then group the remaining comments by file path.
For each affected file:
For each comment:
After editing:
Summarize:
Before applying fixes, look for project-specific conventions by:
Prefer patterns already established in the project over inventing new ones.