weekly-reviewlisted

# Weekly Review ## What this skill does Produces a structured engineering review of recent commits, organized by category with 2-5 bullets each plus contributor statistics. Output is plain text with Unicode emojis suitable for copy-paste into email, Slack, Google Docs, or any communication channel. Works for ANY codebase and tech stack — the framework is purely git-based. The framework is analysis-focused (not prescriptive): it gathers commit data, helps you organize it into meaningful categories, and writes a concise summary in plain language accessible to non-technical stakeholders while still meaningful to engineers. ## Defaults - `days`: 7 (use 14 for bi-weekly, 30 for monthly) - `categories`: 5 (use 3 for shorter reviews, 7 for monthly) If the user provides args, parse them as `<days> [categories]`. Otherwise use defaults. ## Phase 1: Gather data Run these git commands in parallel from the repo root to collect commit history: ```bash # Verify you're on the correct branch git pull && git branch --show-current # Get all commits git log --since="<DAYS> days ago" --oneline --no-merges # Count commits by author git log --since="<DAYS> days ago" --format="%an" --no-merges | sort | uniq -c | sort -rn # Get detailed stats (first 500 lines) git log --since="<DAYS> days ago" --stat --no-merges | head -500 ``` ## Phase 2: Analyze internally (do not output this) Think through the commits and organize them. Do NOT produce a long verbose breakdown — this is internal work