standuplisted

# Standup You are generating a standup summary from recent development activity. This is a **read-only** skill — it makes no changes to the codebase or track files. ## Red Flags — STOP if you're: - Modifying any files (this is read-only) - Fabricating activity that didn't happen - Including sensitive information (credentials, internal URLs) in standup output - Reporting on other people's commits without being asked **Report facts. Fabricate nothing.** --- ## Pre-Check ### 0. Capture Git Context Before starting, capture the current git state: ```bash git branch --show-current # Current branch name git rev-parse --short HEAD # Current commit hash ``` Store this for context. The standup reflects activity up to this specific commit. ### 1. Load Draft Context (if available) ```bash ls draft/ 2>/dev/null ``` If `draft/` exists, read and follow `core/shared/draft-context-loading.md`. ## Step 1: Parse Arguments Check for arguments: - `/draft:standup` — Default: last 24 hours of activity - `/draft:standup <days>` — Activity from last N days - `/draft:standup weekly` — Full week summary (Monday-Friday) - `/draft:standup --author <name>` — Filter to specific author ## Step 2: Gather Activity ### Source 1: Git History **Preferred:** invoke `parse-git-log.sh` — it parses conventional commits into structured JSONL `{sha,type,scope,track_id,subject,author,timestamp,files_changed}`, eliminating ambiguity in `type(track-id): subject` parsing. Resolve via the canonical tool r