agentsclimarketplace

Review address comments

Skill motao123/dev-workflow-kit/review-address-comments

21 markdown-first software delivery workflow skills for Claude Code, Codex, and compatible agents. Standalone skill kit covering planning, debugging, CI, review, security, rollout, performance, data quality, and post-incident workflows.

Install
npx -y skills add motao123/dev-workflow-kit --skill review-address-comments

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

One thing to look at

  • 1 stars1 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.

What its author says it does

Copied from the file, not written here

Use when review comments, requested changes, or PR feedback must be processed systematically. This skill groups comments, decides what to accept, and turns feedback into verified edits instead of ad hoc reactions.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.7 KB, as published. Nobody here has run it

Review Address Comments

Use this skill when collaboration after implementation becomes the main task.

Trigger Conditions

Use this skill when:

  • a PR has reviewer comments
  • the user asks to address requested changes
  • feedback needs to be grouped or prioritized
  • multiple comment threads refer to overlapping concerns
  • the branch needs a clear resolution summary after edits

Do not use this skill for initial implementation planning or for pure status lookups without feedback to process.

Workflow

  1. Gather the comments and group them by theme.
  2. Distinguish must-fix issues from optional suggestions.
  3. Identify overlapping comments and consolidate the work.
  4. Apply the smallest changes that resolve accepted feedback.
  5. Verify each changed area.
  6. Summarize what was addressed and any intentional non-changes.

Output

For non-trivial work, provide:

  • grouped feedback themes
  • accepted vs deferred items
  • edit plan
  • verification evidence
  • resolution summary

Coordination

After comment processing:

  • hand off to the active coding workflow for implementation edits
  • use fix-ci if review-triggered changes break automation
  • use ship-readiness before final merge

Invocation Examples

  • "Use review-address-comments to classify and resolve this PR feedback."
  • "Use review-address-comments and turn these requested changes into an action list."
  • "Use review-address-comments after the last review round and summarize what remains."

Keep looking

Skills are one crate of 328,083. 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.