nntrivi2001
17d56d0e01
Clean break, no compatibility alias. Renames the product name, the CLI binary (`ccam` -> `agenthub`), the env var prefix (`CCAM_` -> `AGENTHUB_`), the Prometheus metric namespace (`ccam_*` -> `agenthub_*`), the tmux session prefix (`ccam-lane-<id>` -> `agenthub-lane-<id>`), the per-repo runtime profile directory (`.ccam/profile` -> `.agenthub/profile`), the lanes state root (`~/.claude/ccam-lanes` -> `~/.claude/agenthub-lanes`), the bundled plugins (`plugins/ccam*` -> `plugins/agenthub*`) and their slash commands (`/ccam-doctor` -> `/agenthub-doctor`, `/ccam:*` -> `/agenthub:*`). Because there is no alias, an existing install has to be updated by hand: rename its `.ccam/profile` directory and any `CCAM_*` variables, and reinstall the plugin under its new name. Two other name families are deliberately left alone here, since they are not just strings: the `Claude-Code-Monitor` repository/marketplace name, and the `agent-dashboard` npm package plus its `~/.claude/agent-dashboard` runtime directory, which holds the live database and needs a migration rather than a rename. Verified: server 1406/1406, client 459/459, `grep -i ccam` clean across tracked files, `openapi.yaml` regenerated (95 paths, unchanged count).
65 lines
2.1 KiB
Markdown
65 lines
2.1 KiB
Markdown
---
|
|
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 AgentHub 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
|
|
|
|
1. **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}`
|
|
|
|
2. **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 `error` or `abandoned` status
|
|
- 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
|
|
|
|
3. **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.
|