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.

33 stars 4 forksMarketing, Sales & Business Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add okgrit/done-is-a-claim

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add okgrit/done-is-a-claim --skill responding-to-review
Manual install
git clone --depth 1 https://github.com/okgrit/done-is-a-claim.git /tmp/done-is-a-claim
mkdir -p ~/.claude/skills
cp -r /tmp/done-is-a-claim/skills/responding-to-review ~/.claude/skills/responding-to-review

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# 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,
classification, supporting observation, next action and status. Use these classes:

- **Substantiated:** current evidence shows a contract defect.
- **Stale:** the referenced issue no longer exists on the current candidate.
- **Disputed:** the proposed change conflicts with the contract or current evidence.
- **Unclear:** missing information materially affects what correction is valid.
- **Scope proposal:** useful new behavior or preference beyond the agreed outcome.

Inspect the implementation and affected consumers; reproduce the claimed defect
or run a discriminating check when needed. Repeated bot comments are the same
claim unless they contain new evidence. Do not implement a suggestion blindly,
count repetitions as confirmation, or manufacture a finding to agree politely.
Read the full skill on GitHub

Details

Skill name
responding-to-review
Path
skills/responding-to-review/SKILL.md
License
Apache-2.0
Repo updated
25 October 2026

FAQ

What does the Responding to Review skill do?

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.

How do I install the Responding to Review skill?

Claude Code plugin: /plugin marketplace add okgrit/done-is-a-claim. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Responding to Review popular?

It lives in okgrit/done-is-a-claim, which has 33 GitHub stars and 4 forks, and is included in 1 curated skill list.

Related skills

Acceptance Design

33

okgrit/done-is-a-claim

Define executable acceptance for a bounded task before work or dispatch. Use when writing a worker brief, selecting success checks, or repairing an acceptance contract that cannot test the intended outcome.

Testing & QAIn 1 list

Checking Delivery

33

okgrit/done-is-a-claim

Verify an artifact at its actual delivery destination and distinguish send attempts, acknowledgements, publication and consumer checks. Use when reporting a file, message, export or deployment as delivered; creating a local draft alone does not imply delivery.

DevOps & CloudIn 1 list

Collecting Worker Results

33

okgrit/done-is-a-claim

Inspect a stopped worker's returned work and evidence before accepting it, retrying it or handing it to an integration owner. Use when a worker finishes, records disagree, or a green result has no visible change. Collection does not authorize merging.

OtherIn 1 list

Business Process Flows

52

korchard333/claude-power-platform-community

Business Process Flows (BPFs). Use when: creating BPFs, BPF stages, BPF branching, cross-entity BPFs, BPF XAML creation via API, BPF activation, BPF client-side JavaScript, process instance management.

Marketing, Sales & Business

Hipaa

33

scytale-labs/GRC-Claude-Skills

Use when the user asks about HIPAA — Privacy Rule, Security Rule (administrative, physical, technical safeguards), Breach Notification Rule, Business Associate Agreements (BAAs), the HITECH Act, OCR audits, or determining whether an organisation is a covered entity or business associate. For US healthcare providers, health plans, clearinghouses, and their business associates and subcontractors.

Marketing, Sales & Business14

Calci Prediction Market

59

ratacat/claude-skills

Context and working knowledge for Calci’s prediction-market domain, which is powered by Kalshi. Use this skill whenever the user asks about Calci prediction markets, Kalshi markets, tickers, order books, pricing, settlement, or the Kalshi API/WebSocket.

Marketing, Sales & Business10

Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.