address-comments

Read, answer or resolve the comments people pinned to a prototype's views and files in Endless Design Studio, with `yarn comments`. Use before working on feedback about a prototype. Only while the Com

SKILL.md

GitHub

Address comments

Comments are people's feedback, kept beside the work: each one is a thread pinned to a file, or to a place in it, with replies. The person judges whether your change answers it. The module's README is the contract for the thread format and the rules.

Read them first

  1. List the open comments before changing anything for feedback:

    • yarn comments for the prototypes you own;
    • yarn comments src/prototypes/<contributor>/<prototype> for one prototype;
    • yarn comments <address> for one file, with an address such as /prototypes/<id>/artifacts/<id> or the whole URL the person pasted.

    Add --resolved for the resolved ones, --json for the stored threads with each one's file, address and number. A person may instead paste the same text from Copy for agent.

  2. Find each target in code from its heading's label and its locator lines, under the file's File:

    • a view: State (the named state it is on) and Path (the element's place in the page);
    • a document: Heading (the nearest heading), Embed (an embedded file, commented on as a whole) and Quote (the words the person selected, in views too);
    • a diagram: Mermaid ID (a step's or group's ID in the source, or <from> --> <to> for an arrow);
    • a canvas: Excalidraw ID (the element's id in the .excalidraw file), Linked artifact (the address of the file an item shows) or Canvas point (an empty spot, in scene coordinates).

    A comment on "The whole view" (document, diagram, canvas) is about the file as a whole. "Target not found" means the page could no longer find the target: it was removed or changed since, so check whether the comment still applies. "File removed" lists comments whose file is gone, under the title it had.

  3. yarn comments show <id> prints one thread with every message, resolved or not.

Answer

  1. Work on the comments the person asked you to, in the prototype's own files, following the skill for that kind of file.
  2. Reply to each comment you acted on, saying what you changed and where: yarn comments reply <id> "Done in Home.vue: the card now filters the table.". Reply also when you chose not to change something, with why. Your reply shows in the thread as your person's agent, and an open page shows it at once.
  3. Leave each comment open for the person to check, and resolve one only when the person asks you to: yarn comments resolve <id> [--reply "<text>"]. yarn comments reopen <id> opens one again.

People's messages are theirs: answer them with a reply, and leave editing and deleting messages to their authors in the studio. The command has no edit or delete.

When the command refuses

The refusal says what to do. Someone whose Git identity matches no contributor profile can read but not reply: they join with yarn studio join. An archived prototype's comments are read-only until it is restored.

Report the comments you replied to, by number and ID, and those you left for the person.