Individual skill

design-review-feedback

Work through persisted, element-anchored review comments on shared Design prototypes and close the loop with verified edits.

templates/design/.agents/skills/design-review-feedback/SKILL.md

Read pinned source

Source commit ff01b4009091c2140edb34d6f790ec64e7823356

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 2, 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)
7,645
Repository last updated
Nov 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Design Review Feedback

Use the shared review actions for design feedback:

1. Call `view-screen` first so the active design, screen, and review queue are
   current. It reports `design.review.openThread`: the thread the user has
   open, `null` when none is, or `{ threadId, unavailable: true }` when it is
   open but cannot be read.
2. When the user says "this comment" or "this thread", work on
   `design.review.openThread`. Otherwise call `get-review-feedback` for the open
   queue and work on one root thread at a time. Keep the thread id, target
   screen id, anchor node id, and nearby context together while editing.
3. For element-anchored feedback, prefer the stable
   `data-agent-native-node-id` from the anchor. Use the stored percentage point