Menu
Responds to PR review comments. Use when addressing reviewer feedback, replying to diff comments, or checking for unaddressed reviews.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Rewrites robotic or AI-sounding text to feel natural while preserving meaning and voice. Use when humanizing or reviewing generated, over-polished, repetitive, or impersonal prose. Covers 24 wording patterns and 14 construction patterns.
Writes, rewrites, drafts, or reviews text in Lachlan's written and spoken voice. Use when the user asks to "talk like me" or "sound like me", or needs Slack replies, emails, leadership notes, technical feedback, customer or strategy messages, meeting comments, or talking points that match Lachlan's directness, dry humour, and evidence-first engineering judgement.
Iteratively review and improve the current PR or branch by running general-code-reviewing, fixing grounded issues, validating, and re-reviewing until the change is merge-ready or a blocker remains. Use when asked to auto-review, self-review and fix, harden, polish, get a PR ready, or iterate on code quality rather than only return review comments.
Draft and revise durable engineering plans. Use for `docs/plans`, architecture, rollout, design docs, first-slice selection, open-question resolution, adversarial pressure-testing, and plan maintenance during implementation.
Run the full code-to-merged-PR workflow: auto-review the current branch or PR, create or update a GitHub PR, babysit it through reviews and CI, merge it, and report the final state. Use when asked to land a PR, land this, ship this branch, get this into a PR and merge it, or otherwise carry code from local changes or a current branch to a merged PR.
Read x.com/twitter.com posts, tweets, quote tweets, and user-provided post URLs through the authenticated xurl CLI, with Birdclaw as the local cache and research fallback. Use when asked to read, summarize, inspect, quote, fetch, or explain an X/Twitter post URL or status ID; when the user says to use their Twitter account; or when read-only Twitter/X context should come from xurl or Birdclaw instead of web search.
| name | addressing-pr-reviews |
| description | Responds to PR review comments. Use when addressing reviewer feedback, replying to diff comments, or checking for unaddressed reviews. |
Reply to PR review comments from human reviewers or automated bots.
# List diff comments (inline on code)
gh api repos/{owner}/{repo}/pulls/{pr}/comments \
--paginate \
--jq '.[] | {id, user: .user.login, path, line, body: .body[0:100]}'
# Get full diff comment body
gh api repos/{owner}/{repo}/pulls/comments/{comment_id} --jq '.body'
# List top-level review comments (not on specific lines)
gh api repos/{owner}/{repo}/pulls/{pr}/reviews \
--paginate \
--jq '.[] | select(.body != "") | {id, user: .user.login, state, body: .body[0:200]}'
# Get full review body
gh api repos/{owner}/{repo}/pulls/{pr}/reviews/{review_id} --jq '.body'
Always reply inline to the specific comment.
For all reviewers (human or bot), use a normal inline reply without @codex:
gh api repos/{owner}/{repo}/pulls/{pr}/comments \
-f body="Fixed in {commit}: {explanation}" \
-F in_reply_to={comment_id}
Use @codex only when you explicitly want to trigger a Codex action.
For top-level review comments (not on specific lines), use a normal PR comment:
gh pr comment {pr} --body "Fixed in {commit}: {explanation}"
Acknowledge valid feedback with a thumbs up:
gh api repos/{owner}/{repo}/pulls/comments/{comment_id}/reactions \
-f content="+1"
For inaccurate Codex feedback, use thumbs down:
gh api repos/{owner}/{repo}/pulls/comments/{comment_id}/reactions \
-f content="-1"
For human reviewers:
gh pr edit {pr} --add-reviewer {username}
For Codex, trigger exactly one explicit review request after batching fixes:
gh pr comment {pr} --body "@codex review"
Note: reviewer account names can vary by setup; do not hard-code a single bot username.
Codex GitHub behaviour is:
@codex review requests a review run.@codex with anything else starts a Codex cloud task.Do not post routine fix replies like:
@codex Fixed in {commit}: {explanation}
That can create noisy task-output comments (for example, "Summary", "committed on branch", "opened follow-up PR") that do not reflect actual repo state.
Use this instead for routine updates:
Fixed in {commit}: {explanation}
Then, after batching fixes, post exactly one:
@codex review
@codex review@codex in routine "fixed" repliesImportant: Don't amend commits after replying - the referenced commit hash becomes invalid.