client-report-from-commits

Turn git history for a resolved date range into a copy-pastable, non-technical client update grouped by feature.

Decision Tree

What do you know already?

Exact start date in YYYY-MM-DD and the current working directory is the target git repo: continue.
Exact start date in YYYY-MM-DD, but the target repo is elsewhere: use the explicit repo path and continue.
Unambiguous relative date with a reliable clock, timezone, and relevant context: resolve it and state the exact YYYY-MM-DD boundary and timezone before collecting history. No redundant confirmation is needed.
Genuinely ambiguous range such as "recently", an unspecified week boundary, or "since the last push" without a known event boundary: ask a focused question. Do not guess a push or deployment date from commit timestamps.
No readable git repo in the current working directory and no repo path was provided: stop and ask for a readable git repository path.
The user wants engineering release notes, a developer changelog, or a code review: do not use this skill.