agentsclimarketplace
Sign in

Skill address pr review

Skill mnapoli/skill-address-pr-review

Look at the pull request review comments and address any issues raised.From its SKILL.md

Install
npx -y skills add mnapoli/skill-address-pr-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 3 commands, including `bash ./get-unresolved-threads.sh` and 2 more.

SKILL.md

2.0 KB, 440 tokens by cl100k_base, as published. Nobody here has run it

Step 1: Fetch unresolved review threads and CI status

Run both helper scripts:

bash ./get-unresolved-threads.sh

bash ./get-failing-ci.sh

The first returns a JSON array of unresolved threads. Each thread has:

  • id — thread ID (needed to reply)
  • path — file path
  • line / startLine — line numbers in the diff
  • isOutdated — whether the diff has changed since the comment
  • comments.nodes[] — the comment thread (first = original comment, rest = replies), each with author.login, body, and url

The second checks CI status and outputs failure details if any jobs failed (exit code 1 = failures, 0 = all passed).

If there are no unresolved threads and CI is green, stop here.

Step 2: Address each issue

If there are many items, create one task per item to keep things organized.

For each unresolved review thread:

  1. Read the comment thread to understand the issue
  2. Determine if a code change is needed, or if no change is needed (e.g. the comment is invalid or the suggestion is not appropriate)
  3. If a change is needed, make the necessary code changes

For each CI failure:

  1. Read the failure output to understand what broke
  2. Fix the code or tests to make CI pass

Step 3: Commit and push changes

After addressing all review comments and CI failures, commit your changes and push.

Step 4: Reply to each review thread

After addressing each comment, reply using the helper script:

bash ./reply-to-thread.sh "<thread_id>" "<body>" [--resolve]
  • If the code was fixed as mentioned in the thread, reply with simply: "Fixed as suggested." and pass --resolve to mark the thread as resolved.
  • If no change was applied, briefly explain why and keep the thread unresolved (omit --resolve) so the reviewer can reply if they disagree.
  • Don't be unnecessarily verbose.

What ships with it: 6 files

295.0 KB alongside SKILL.md, 3 of them executable

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.