Menu
Address pull request review comments
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Run jj commit. Use when current work is ready to commit and Codex should inspect the changes, use any provided context, and create a reasonable detailed Jujutsu commit message.
Commit changes, push to remote, and create a PR skill
Create a set of phases for a large project
Read a PR review guide and review the code. Use when `review-guide.md` already exists and Codex should follow that guide, inspect the referenced changes, and append findings without overwriting prior notes.
Fix merge conflicts. Use when the current repository has unresolved conflicts and Codex should inspect both sides, trace the surrounding history, resolve the files carefully, and ask for help only when the correct resolution is unclear.
Address AI review comments in source files. Use when repository files contain AI review markers and Codex should locate them, implement the requested fixes, remove the markers, and validate the changes.
| name | address-pr-review |
| description | Address pull request review comments |
You are addressing review comments on a pull request for the current branch.
To resolve the PR from the current working copy:
jj bookmark list --revisions @- to find the current jj bookmark.@-, run jj log -r 'ancestors(@) & bookmarks()' --no-graph --limit 5 and use the nearest bookmark that represents the pushed branch.gh pr view <bookmark> --json number,title,headRefName,baseRefName,url,author,reviewDecision.gh pr view <bookmark> --comments and, when line-level review context is needed, use gh api repos/:owner/:repo/pulls/<number>/comments.gh api repos/:owner/:repo/pulls/<number>/reviews.After fetching the review comments and related feedback, list the comments for the user before making code changes. Include enough context to distinguish each item, such as author, file, line, comment summary, and whether it is a review-thread comment or general PR feedback.
Ask the user for feedback on which review comments to address and how. If the user has already given clear instructions, follow those instructions; otherwise wait for direction before implementing fixes.
main.Do not mark review comments or threads resolved. Do not update the status of the issue or PR. Do not request or re-request reviews.
Block comments are used when a review comment applies to multiple lines of code, to make it easier to see which code is being referenced. A single line comment may also apply to multiple lines of code; you infer from the comment and surrounding code what is desired. In both cases, consider all relevant information to make the proper change--your changes can update other related code if that is appropriate.
When done, print the Github URL for the PR, but use https://linear.review as the domain instead of https://github.com.