comments
/comments
Draft, refine, or respond to pull-request review comments. Use when a user asks to "write a review comment", "address review feedback", or "reply to a reviewer".
- Author
- jl-cmd-projects ↗
- Repository
- claude-dev-env ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Draft, refine, or respond to pull-request review comments. Use when a user asks to "write a review comment", "address review feedback", or "reply to a reviewer".
Triggers from the description
Original author description
Draft, refine, or respond to pull-request review comments. Use when a user asks to "write a review comment", "address review feedback", or "reply to a reviewer".
How it works
- When to Use This Guide
- Writing Useful Review Comments
- Respectful and Actionable Feedback
- Responding to Feedback
- Resolving Pushback
- Related Guides
SKILL.md preview
--- name: comments description: >- Draft, refine, or respond to pull-request review comments. Use when a user asks to "write a review comment", "address review feedback", or "reply to a reviewer". --- # Review Comment Guide ## When to Use This Guide Use this guide to draft a finding, refine its tone, reply to reviewer feedback, or resolve a comment thread. Use the [review guide](../reviews/SKILL.md#review-judgment) to decide whether a concern merits a finding. ## Writing Useful Review Comments Each comment names the affected behavior, the observed concern, the relevant evidence, and the expected outcome. Give the author enough context to choose an effective fix. - Use `Required` for a change that materially affects the review judgment. - Use `Consider`, `Nit`, or `FYI` for improvement, polish, and context. - Explain the technical rationale when the connection from evidence to outcome needs context. - Recognize strong decisions and completed fixes with the same specificity. ## Respectful and Actionable Feedback Treat every contributor as capable and acting in good faith. Keep feedback about the code, its behavior, and its effect on users or maintainers. - Consolidate a disagreement into one focused exchange with the relevant context and reasoning. - Use proportionate language that directs attention to the required change. - Respect repository tooling and established formatting conventions. - Close a thread when its outcome satisfies the applicable review judgment. ## Responding to Feedback Start with the substance of the feedback. Clarify the code, its tests, or its documentation when that gives future readers the needed context. Ask for clarification when the requested outcome remains unclear. Reply with the trade-off, evidence, and proposed resolution when an alternative approach better serves the stated goal. ## Resolving Pushback Reassess a disputed finding against the repository rubric and the change's evidence. Keep advocating for a material improvement when the rationale remains sound, and accept an evidence-backed alternative that meets the same quality goal. Escalate to a maintainer or lead when product direction or code ownership is needed. Record the resulting decision in the pull request thread. ## Related Guides - Use [reviews](../reviews/SKILL.md#review-workflow) for substantive code assessment. - Use [pr-small-cl](../../skills/pr-small-cl/SKILL.md#responding-to-review) for author-side review responses and focused follow-up work. - Use [emergencies](../emergencies/SKILL.md#while-the-incident-is-active) for urgent production-change communication.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · jl-cmd-projects/claude-dev-env | 90 | MIT |
| fubits1/svelte-skills | 100 | MIT |
| anthropics/claude-for-legal | 100 | Apache-2.0 |
| uk-agents/uk-legal-plugins | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 8c9adbe8d915 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 84reply
This skill should be used when the user asks to "reply to PR comments", "respond to review comments", "reply to PR #123", "answer PR feedback", or wants to respond to unresolved review threads or comments from other users on a pull request. - 100address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI. - 100review-pr-comments
Address review comments on a GitHub pull request — fetch unresolved comments, investigate each issue, fix valid ones, reply, and resolve threads. Use this skill when the user asks to review PR comments, address PR feedback, handle PR review, respond to reviewer comments, or fix… - 100prc
Review and address code review comments on PR. Use when asked to 'address review comments', 'fix PR feedback', 'handle review comments', 'respond to PR comments', or 'address CR comments'. NOT for initiating code review (use /sr), NOT for task-based implementation with CR mode (use /si). - 100prc
Review and address code review comments on PR. Use when asked to 'address review comments', 'fix PR feedback', 'handle review comments', 'respond to PR comments', or 'address CR comments'. NOT for initiating code review (use /sr), NOT for task-based implementation with CR mode (use /si). - 100stacked-pr-review
Use when addressing PR review comments on stacked jj branches. Triggered by phrases like "address review comments", "fix PR feedback", "respond to review on stacked branch", or "update the PR with reviewer suggestions".