end-of-day-recap

Turn a day of scattered activity — commits, MRs, closed tickets, comments, ops — into a recap someone can read in fifteen seconds.

This is a read-only synthesis skill. It gathers evidence, clusters it by work item, and writes a tight recap. It never invents work, never closes tickets, never pushes. Most people using this are not only writing code — they live in ClickUp, meetings, and ops — so git is one input, not the input.

The output (this is the whole point)

Exactly this shape. Two short paragraphs, then ~5 numbered bullets. No preamble, no "Here's your recap," no filler adjectives.

<One sentence: the day's theme.> <One sentence: impact or the handoff for tomorrow.>

<Optional second paragraph ONLY if there's a real blocker, decision, or thing the reader must act on. Otherwise stop at one.>