work-report

Write the work report, WORK-REPORT.md at the working tree root: what the diff cannot show, for a reviewer or fresh session. One per tree, overwritten each run, so it reads as current state. Any directory (git or not, worktree or not), any shape of work (commits, loose edits, cross-repo changes, editor settings).

Follow the steps in order. Stop only on an unwritable path; missing git, no repo, or a quiet session still get a valid report.

Never write without being asked

Self-activated (user signalled work finished without naming the report): offer in one sentence, wait for a go-ahead. You may read the existing report first so the offer carries the Step 2 question. An explicit invocation (/work-report, "write the work report") is the go-ahead.

Scope of "the work" = this chat session

Report what you did this session. Never infer it from git diff or git log: git already records that, and reconstruction loses the intent. A free-text note passed with the invocation sets emphasis (that topic leads each section), never narrows scope.