feat: Claude Code Monitor — lanes, pipelines and a merged workspace
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.
This commit is contained in:
@@ -0,0 +1,73 @@
|
||||
---
|
||||
description: >
|
||||
Compile a weekly productivity report using Agent Monitor data — daily_sessions
|
||||
and daily_events trends, per-session costs from pricing engine, token volumes
|
||||
(input/output/cache_read/cache_write + baselines), tool usage top 20,
|
||||
session completion rates by status, and workflow intelligence metrics.
|
||||
---
|
||||
|
||||
# Weekly Report
|
||||
|
||||
Generate a comprehensive weekly productivity report from Agent Monitor data.
|
||||
|
||||
## Input
|
||||
|
||||
The user provides: **$ARGUMENTS**
|
||||
|
||||
This may be:
|
||||
- "this week" or empty (default: current week Mon-Sun)
|
||||
- "last week" for the previous week
|
||||
- A date range: "2025-04-07 to 2025-04-13"
|
||||
|
||||
## Procedure
|
||||
|
||||
1. **Fetch weekly data** from `http://localhost:4820`:
|
||||
- `GET /api/sessions?limit=200` — filter to target week (default sort: most recently updated first)
|
||||
- `GET /api/analytics` — aggregated analytics
|
||||
- `GET /api/pricing/cost` — cost data
|
||||
|
||||
2. **Build the weekly report**:
|
||||
|
||||
### 📊 Week at a Glance
|
||||
| Metric | This Week | Last Week | Change |
|
||||
|--------|-----------|-----------|--------|
|
||||
| Sessions | N | N | ↑/↓ N% |
|
||||
| Total Hours | N | N | ↑/↓ N% |
|
||||
| Tokens Used | N | N | ↑/↓ N% |
|
||||
| Total Cost | $X.XX | $X.XX | ↑/↓ N% |
|
||||
| Completion Rate | N% | N% | ↑/↓ |
|
||||
|
||||
### 🏆 Highlights
|
||||
- Most productive day (by sessions completed)
|
||||
- Longest session and what it accomplished
|
||||
- Most used tools and any new tools adopted
|
||||
- Notable achievements (complex tasks completed, errors resolved)
|
||||
|
||||
### 📈 Daily Breakdown
|
||||
| Day | Sessions | Hours | Cost | Completion |
|
||||
|-----|----------|-------|------|------------|
|
||||
For each day of the week with activity.
|
||||
|
||||
### 🔧 Tool Usage Report
|
||||
- Top 10 tools by invocation count
|
||||
- Tools with highest error rate
|
||||
- Tool usage distribution chart (text-based)
|
||||
|
||||
### 💡 Productivity Insights
|
||||
- Peak productivity hours
|
||||
- Average session duration and trend
|
||||
- Cost efficiency trend
|
||||
- Model usage distribution
|
||||
|
||||
### 🎯 Recommendations for Next Week
|
||||
- Based on error patterns: what to improve
|
||||
- Based on cost trends: optimization opportunities
|
||||
- Based on tool usage: workflow suggestions
|
||||
|
||||
## Output Format
|
||||
|
||||
Professional report format with:
|
||||
- Executive summary (3 sentences max)
|
||||
- Structured tables with week-over-week comparisons
|
||||
- Emoji-prefixed section headers for scannability
|
||||
- Actionable recommendations in priority order
|
||||
Reference in New Issue
Block a user