Use when writing, structuring, or optimizing Korean Naver Blog posts, especially daily-life posts, restaurant reviews, cafe reviews, travel/visit reviews, and posts where the user provides only feelings plus images and wants a complete post with image slots, search-backed facts, title candidates, tags, and publish settings.
Use when a task requires visual verification with screenshots, especially frontend UI changes, local app previews, responsive layout checks, rendered assets, canvas or 3D output, browser-based QA, or before/after proof for review. Guides Codex to run the target, inspect it in a real browser or app surface, capture screenshots at relevant states and viewports, and report concrete evidence instead of relying on implementation-only claims.
PR/diff를 기능 단위로 재구성하고, 기능별 리뷰 축을 병렬로 펼쳐 리뷰 포인트를 발굴한 뒤, 각 포인트를 코드/테스트/런타임 증거로 검증해 확정 finding을 만든다. Triggers: - "리뷰해줘" - "PR 리뷰" - "코드리뷰" - "전반적으로 리뷰 포인트 잡아줘" - "기능 단위로 리뷰해줘" - "review assistant"
Use when working with git worktrees - creating isolated workspaces for branches, managing multiple features in parallel, or cleaning up worktrees
PR, branch, diff, or repository scope에서 죽은 코드, 고아 코드, 불필요한 코드, wet하게 반복된 코드, 과도한 diff를 줄일 수 있는 삭제/축소 후보를 기능 단위로 찾고 검증한다. Triggers: - "dead code" - "deadcode" - "죽은 코드" - "불필요한 코드" - "diff 줄여줘" - "코드 줄일 수 있는지 봐줘" - "wet code" - "dead-code-detector"