aryaminus Standup Summary
Summarize work over a time period. Enriches git log with CK session data for richer context than git alone.
Do NOT use when
- During coding, review, or planning tasks
- The user wants code changes (not a summary)
Workflow
- Resolve time window from user input. Default: yesterday.
- Read git commits by current user in range:
git log --author="$(git config user.email)" --since="<start>" --until="<end>" --no-merges --format="%h %s" - Enrich with CK data:
ck_session_digest(mode:generate) for session tasks, findings, budgetck_outcome_tracker(mode:get_session) for session outcomes and approval patternsck_memory_searchfor active decisions in the time window
- Synthesize: prioritize substantial changes, omit cosmetic-only.
- Output format:
## Standup: <start> – <end> <one sentence summary> ### Shipped - <2-5 bullets, major changes only> ### In progress / Blocked - <if any>
Guardrails
- Every bullet traces to a commit or CK record — no fabrication
- Do not infer intent — describe changes functionally
- If no activity in range, say so clearly
Output
- Concise status update with real date range
- 2-5 major bullets for substantial changes