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".
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- 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".
03 SKILL.md 正文
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 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
Requiredfor a change that materially affects the review judgment. - Use
Consider,Nit, orFYIfor 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 for substantive code assessment.
- Use pr-small-cl for author-side review responses and focused follow-up work.
- Use emergencies for urgent production-change communication.
04 同仓库更多 Skills
update
Fast-forwards a local repository's main branch to a remote's main after confirming the repo path and source remote through AskUserQuestion. Use when the user says '/update', 'update main', 'fast-forward main', 'sync main from origin', 'pull latest main into <path>', or 'bring main up to date'.
source-command-sr-loop
Converging cleanup loop: repeat /simplify until clean, then repeat /code-review --fix until clean
skill-builder
Skill lifecycle: classify, scaffold, write via the skill-writer-agent, self-audit, compose sub-skills, polish description triggers, enforce deterministic scripts. Triggers: build a skill, new skill workflow, improve this skill, optimize skill description, skill development lifecycle, skill modularity, skill composition, description trigger catalog, deterministic skill scripts.
session-tidy
Audit, clean, and consolidate session logs in the Obsidian vault. Fixes format drift, resolves orphaned next-steps, updates stale statuses, and generates project rollup summaries. Use when session logs feel cluttered or before starting a new project milestone. Triggers on '/session-tidy', 'tidy sessions', 'clean up session logs', 'session audit'.
session-log
Logs a session report as an HTML page, tracks vault context, extracts decisions, and outputs a /rename command. Use for /session-log, 'journal this session', 'log this work', 'session report', 'summarize/log/record this session', 'save session', 'capture session', or 'document what we did'.
run-claude-dev-env
Build, install, run, and test the claude-dev-env installer. Use when asked to run claude-dev-env, install the Claude Code config into ~/.claude, drive the installer, smoke-test it against a sandbox, or run its test suite.