Interpret Feedback

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

Emit both Agent tool calls below in one assistant message. Each Agent call uses model: "opus" and no name. Wait for every agent to report before continuing. Do not begin the next step on a partial set, and do not relaunch an agent that has not yet reported. That is two Agent tool calls total. Both agents' prompts must direct them to treat the shared working tree and its git index as read-only and to interpret by reading and reasoning. HEAD stays where it is: read other refs with git show <ref>:<path> rather than git checkout or git switch.

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: Whether the suggestion is technically sound — flag concerns if the reviewer may be mistaken, with evidence
   • Ambiguity: Note where the intent is unclear or where multiple valid readings exist
3. Return structured results per item

Run /peer-review Skill

Launch an Agent tool call whose prompt instructs the subagent to invoke /peer-review via the Skill tool. Describe the request in natural language:

• Material — the listed third-party feedback items and their surrounding context.
• Task — for each item, determine what the author most likely wants changed and why, whether the suggestion is technically sound, and where the phrasing is ambiguous enough to support multiple valid readings.
• Skepticism guidance — do not take feedback at face value. Check whether the author's stated concern matches the code reality. Look for cases where the reviewer misread the code, confused two similar constructs, or applied a general rule that does not fit this specific context.
• Output format — for each feedback item, return:
  1. Intent — what the author most likely wants changed and why (one to two sentences)
  2. Correctness — whether the suggestion is technically sound. If not, explain what the reviewer likely misunderstood, with evidence from the code
  3. Ambiguity — if the intent supports multiple valid readings, list each reading and which has stronger evidence