Individual skill
responding-to-review
Resolve incoming code-review feedback against the current revision and user contract. Use to assess comments, implement authorized fixes, explain supported disagreement and verify item status; review does not authorize posting replies.
skills/responding-to-review/SKILL.md
Source commit 14c75a97ccbcca4c11daca25a93c8f0da5ad70d1
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 33
- Repository last updated
- Oct 25, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agents-md Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- claude-md Repository topic
- codex Repository topic
- coding-agents Repository topic
- llm Repository topic
- testing Repository topic
- verification Repository topic
- agent-skills Repository topic
- legal Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,325 bytes
Read excerpt
# Responding to review
Treat a comment as a claim to investigate. Resolve supported findings and retain
the evidence for decisions; neither the author's confidence nor a reviewer's
authority establishes the current behavior.
## Bind each item to the candidate
Read the original outcome, acceptance and preservation requirements, current
revision, dirty inputs, diff and file ownership. Locate each comment's referenced
revision and code. A finding on an old patch may remain relevant, so inspect its
current equivalent before dismissing it or applying an obsolete suggestion.
Keep a compact per-item record: comment identifier, current code locator,