Manual Feedback

Add teaching-team feedback to generated evaluation reports and patch it into existing eval repositories.

Manual feedback lets course staff add direct notes to generated evaluation reports without changing plugin output. It is meant for human feedback such as “try extracting this into a helper” or “this applies to everyone in this milestone”.

Unlike plugin feedback, manual feedback is authored in the origin repository and then patched into generated eval repositories. The report renders it as a separate teaching-team thread, above generic plugin feedback.

Author Feedback

Use the interactive command when selecting a distribution or members manually:

divekit feedback

For repeatable scripts, use the subcommands directly:

# Feedback for one UUID
divekit feedback add -d ST2M4 \
  --member 5c8fc911-c4da-44be-b76d-c6d2d1c9e1f1 \
  --message "Try extracting this into a helper function."

# Feedback for all reports in the distribution
divekit feedback add -d ST2M4 \
  --all \
  --message "Remember to explain your design choices."

# Markdown from a file
divekit feedback add -d ST2M4 \
  --member 5c8fc911-c4da-44be-b76d-c6d2d1c9e1f1 \
  --message-file feedback/note.md

Targets are distribution UUIDs from members.json and remotes.json. When the CLI has a members file for the distribution, the interactive member picker lets you search and select from the configured UUIDs and aliases. Use UUIDs in stored configs and scripts; aliases are only a convenience at the command line.

Inspect, Copy, and Remove

List locally authored feedback before patching:

divekit feedback list -d ST2M4
divekit feedback list -d ST2M4 --all
divekit feedback list -d ST2M4 --member 5c8fc911-c4da-44be-b76d-c6d2d1c9e1f1

Copy feedback from one UUID to others:

divekit feedback copy -d ST2M4 \
  5c8fc911-c4da-44be-b76d-c6d2d1c9e1f1 \
  --member a70decaf-bad7-4c95-b211-d0bc95f48204

Remove one feedback item by id:

divekit feedback remove feedback-20260601t100000z -d ST2M4 \
  --member 5c8fc911-c4da-44be-b76d-c6d2d1c9e1f1

Patch Feedback Into Eval Repositories

divekit feedback only edits local authored feedback files in the origin repository. Run divekit patch feedback afterwards to update existing eval repositories:

# Patch all authored feedback, including global and individual feedback
divekit patch feedback -d ST2M4

# Preview without pushing
divekit patch feedback -d ST2M4 --dry-run

# Patch only one UUID
divekit patch feedback -d ST2M4 \
  --member 5c8fc911-c4da-44be-b76d-c6d2d1c9e1f1

Without --member or --user, divekit patch feedback patches all authored feedback. That includes feedback for all reports and feedback for individual UUIDs. The confirmation plan shows how many global and individual feedback items will be distributed and how many eval targets are affected.

Storage

Authored feedback is stored in the origin repository:

.divekit/distributions/<distribution>/feedback/
├── _all.json
└── <uuid>.json

_all.json stores feedback that applies to every eval report in the distribution. <uuid>.json stores feedback for one distribution UUID.

When patched, eval repositories receive runtime feedback here:

.divekit/feedback/index.json

The report reads that runtime file during divekit report. Global feedback and individual feedback are merged into one teaching-team thread, sorted by timestamp. Messages authored for all reports are marked with an “An alle” badge.

Last modified July 13, 2026: fix: use CLI doc adapter (19a8086)