Agent skill · Code Review & Quality

interpret-feedback

Interpret third-party feedback by running parallel internal and peer interpretations to surface intent, correctness concerns, and ambiguities. Use when the user asks to \"interpret feedback\", \"interpret comments\", \"what does this feedback mean\", \"clarify reviewer intent\", \"understand this review\", or \"interpret these suggestions\".

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill interpret-feedback --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/analysis/interpret-feedback/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Interpret Feedback Run two independent interpretations of third-party feedback in parallel (internal + codex peer), then reconcile into enriched items with clear intent summaries. Designed for feedback where the author's intent is ambiguous or the correctness of suggestions is uncertain. ## Step 1: Identify Feedback Items Determine the feedback to interpret: - If feedback items are in conversation context, use them - If a file path or URL was provided, read or fetch the content - If called by another skill, use the items passed in For each item, collect whatever context is available: code snippets, diffs, surrounding discussion, file paths, line numbers. More context produces better interpretation. ## Step 2: Run Two Interpretations in Parallel Run both interpretation branches independently. Launch them with `spawn_agent` / `wait_agent` using inherited model defaults. ### Internal Interpretation Spawn a subagent with the feedback items and all available context. Instruct it to: 1. Read all referenced code and surrounding context 2. For each feedback item, produce: - **Intent**: What the feedback author most likely wants changed and why (one to two sentences) - **Correctness**: Wh

What's inside
Steps it walks through
  1. Step 1: Identify Feedback Items
  2. Step 2: Run Two Interpretations in Parallel
  3. Internal Interpretation
  4. Run $peer-review Skill
  5. Step 3: Reconciliation
  6. Step 4: Output Enriched Items
  7. Rules
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the interpret-feedback skill do?

Interpret third-party feedback by running parallel internal and peer interpretations to surface intent, correctness concerns, and ambiguities. Use when the user asks to \"interpret feedback\", \"interpret comments\", \"what does this feedback mean\", \"clarify reviewer intent\", \"understand this review\", or \"interpret these suggestions\".

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill interpret-feedback --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going