Personal Commit Review

Write a short Markdown retrospective of a person's GitHub work. Make it read like a written review, not a changelog and not a bullet-only summary.

Default Behavior

• If the user does not specify a time period, default to the last 7 days and say so plainly.
• Default deliverable: one Markdown note, about one page total, usually 400-700 words.
• Use scripts only when they materially help. This skill is primarily a workflow for gathering evidence and writing well.

Workflow

1. Set the review window

• If the period is ambiguous, ask once. If asking would only slow down an otherwise straightforward request, default to the last 7 days and state the assumption.
• Prefer exact --since and --until dates for weekly, monthly, quarterly, or release reviews.
• Decide whether the user wants the review only in chat or also written to a Markdown file.

2. Gather the contribution map