pr-operations_skill

Overview

This skill helps engineers manage pull request review threads and discussion comments using the erk exec command set. It enforces using erk exec for replies and resolutions so threads are properly closed and PR history stays accurate. Use it to fetch unresolved threads, reply to discussion comments, create inline comments, and resolve review threads in one step.

How this skill works

The skill maps common PR thread operations to specific erk exec commands that both post comments and update thread state. It fetches unresolved review threads or top-level discussion comments, posts inline feedback, and — critically — resolves threads using erk exec resolve-review-thread so threads are marked resolved. Avoid raw gh api or gh pr commands for thread resolution because they only add replies and do not change thread status.

When to use it

• When collecting all unresolved code review threads to plan work
• When replying to PR discussion comments that are not tied to code lines
• When you need to post a new inline comment that should create a review thread
• When you must reply and mark a review thread resolved in one operation
• When batching review fixes from simple to complex changes

Best practices

• Always use erk exec resolve-review-thread to reply and resolve; never use gh api or gh pr for resolving
• Fetch unresolved threads first with erk exec get-pr-review-comments to avoid missed items
• Classify comments into batches (local, multi-location, cross-cutting, related) and process from simplest to most complex
• Auto-proceed on Batch 1–2 changes; require an explicit plan and approval for Batch 3–4
• When resolving, include concise action notes and reference commits or PR change IDs for clear history

Example use cases

• Audit PR and list unresolved code review threads: erk exec get-pr-review-comments
• Reply to a top-level discussion comment: erk exec reply-to-discussion-comment --comment-id 12345 --reply "Action taken: updated docs"
• Post a new inline comment to start a review thread: erk exec post-pr-inline-comment --line 42 --comment "Consider adding a type check"
• Resolve a review thread after fixing code: erk exec resolve-review-thread --thread-id PRRT_abc123 --comment "Fixed in commit abc1234"
• Process a batch of typos and small fixes automatically, then present a plan for cross-cutting changes for approval