nntrivi2001
57dc91585d
Internal SmartGift build of a Claude Code monitoring dashboard. Lanes: a durable unit of parallel agent work, one per working directory, tracked across session restarts. Managed lanes are git worktrees the dashboard provisions and can reset or remove behind a three-check destroy guard and a counted preflight; adopted lanes are directories you already own and are never destroyable. Pipelines: a lane moves through pipeline stages. A stage the agent declares with evidence renders green; a stage inferred from the tool-event stream renders dashed amber and never counts as done. Detection is forward-only within a 30-minute window, and never writes the declared stage. Workspace: one page at /run with a lane grid, the selected lane's pipeline, and a full Claude console behind a disclosure.
2.1 KiB
2.1 KiB
description
| description |
|---|
| Generate a daily standup summary from recent Claude Code sessions — completed work grouped by project (cwd), session costs from the pricing engine, tool invocations, error/compaction/APIError events, and turn velocity metrics from session metadata (turn_count, total_turn_duration_ms). |
Daily Standup
Generate a daily standup report from Claude Code Agent Monitor data.
Input
The user provides: $ARGUMENTS
This may be:
- "today" or empty (default: last 24 hours)
- "yesterday" for the previous day
- A specific date: "2025-04-10"
Procedure
-
Fetch recent session data from
http://localhost:4820:GET /api/sessions?limit=50(default sort: most recently updated first)- Filter sessions that started within the target day
- For each matching session:
GET /api/events?session_id={session_id}
-
Compile standup sections:
✅ What I accomplished
- List each completed session with:
- Brief description (from session name or first tool's context)
- Working directory (project context)
- Key tools used and outcomes
- Duration and model used
- Group by project/working directory if multiple
⚠️ Issues encountered
- Sessions that ended in
errororabandonedstatus - Tools that failed (from error events)
- Compaction events (hit context limits)
- Unusually long sessions (>2x average duration)
📋 Key metrics
- Total sessions: N
- Total time spent: X hours Y minutes
- Tools invoked: N (top 3 listed)
- Estimated cost: $X.XX
- Completion rate: N%
🔮 Suggested focus areas
- Based on incomplete/error sessions, suggest what to revisit
- Based on tool patterns, suggest workflow improvements
- List each completed session with:
-
Format for standup:
- Keep it concise — aim for a 2-minute read
- Lead with accomplishments
- Be honest about blockers
- Make metrics scannable
Output Format
Present as a clean standup report with emoji section headers, bullet points for items, and a compact metrics table. Add a one-line summary at the top suitable for pasting into Slack or a team channel.