process-feedback

Process Feedback

Drain the feedback queue that Ghoztty's viewer-pane feedback button produces, one report at a time, in the current worktree.

Each pass handles exactly one report and then resets context, so every report starts with a full context budget. The loop is:

claim oldest  →  plan  →  reproduce  →  fix (TDD)  →  validate  →  complete  →  /reset-context /process-feedback

Queue layout

The producer (Ghoztty) only ever writes new/. This skill owns the rest.

<repo-root>/temp/feedback/
    .staging/            producer's scratch — NEVER read or claim from here
    new/                 unclaimed reports (producer writes here)
    in-progress/         claimed; at most one, and it is yours
    complete/            done and committed
    blocked/             needs the user; see blocked.md inside

A report folder is self-contained:

20260721T214512Z-a3f9c2/
    report.json
    images/image-1.png

Reports are published atomically — do not sleep, poll, or debounce. ViewerFeedbackReport.write builds the whole folder under temp/feedback/.staging/<stem> and publishes it with a single rename(2) onto the same filesystem. A folder visible in new/ is therefore complete by construction, every image already on disk. There is no partially-populated window to wait out and no separate "ready" directory is needed. Two cheap guards cover everything else: ignore any entry whose name starts with ., and require report.json to exist before claiming.

Folder names sort lexically = chronologically (yyyyMMddTHHmmssZ-<hex>), so the oldest report is simply the first name in sorted order.

Instructions

Step 1: Locate the queue and check for an interrupted report

root=$(git rev-parse --show-toplevel) || exit 1
q="$root/temp/feedback"
mkdir -p "$q/new" "$q/in-progress" "$q/complete" "$q/blocked"
echo "QUEUE=$q"
echo "--- in-progress ---"; ls -1 "$q/in-progress" 2>/dev/null
echo "--- new ---";         ls -1 "$q/new" 2>/dev/null | grep -v '^\.' || true