interpret-feedback

Solid

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".

Code & Development 377 stars 29 forks Updated today MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
86
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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 Use the Agent tool to launch both agents below in a single assistant message so they run concurrently. Run them in the foreground so all their results return in this turn. Each Agent call uses `model: "opus"` and no `name`. 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. ### 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...

Details

Author
tobihagemann
Repository
tobihagemann/turbo
Created
4 months ago
Last Updated
today
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category