55 lines
2.7 KiB
Markdown
55 lines
2.7 KiB
Markdown
---
|
|
name: checkout
|
|
description: Build a weekly checkout/review covering Sunday through today. Gathers meetings, emails, Zulip conversations, and Gitea activity, then produces a structured summary.
|
|
disable-model-invocation: true
|
|
---
|
|
|
|
# Weekly Review Builder
|
|
|
|
Build my weekly checkout covering Sunday through today.
|
|
|
|
1. **Get my identity** with `contactdb_get_me` to obtain my contact_id
|
|
2. **Determine date range**: Sunday to today (use `date -d "last sunday" +%Y-%m-%d`)
|
|
3. **Gather activity in parallel**:
|
|
- **Dataindex**: Launch **one subagent per day** (Sunday through today). Each subagent should query `dataindex_query_entities` for that specific day with my contact_id, looking for meetings, calendar events, emails, documents. Return day-by-day summary.
|
|
- **Threaded Conversations**: Launch **one subagent per day** (Sunday through today). Each subagent should:
|
|
1. Query `dataindex_query_entities` for entity_type `threaded_conversation` for that specific day with my contact_id
|
|
2. For each conversation found, fetch all `conversation_message` entities using the conversation ID as parent_id filter
|
|
3. Return messages I participated in with context
|
|
- **Gitea**: Launch one subagent to run `~/bin/gitea-activity -s START -e END` and extract commits, PRs (opened/merged/approved), and repositories worked on
|
|
4. **Query dataindex directly** for the full week as backup to ensure nothing is missed
|
|
|
|
**Output location**: Write the checkout to `checkouts/checkout_$(date +%Y-%m-%d).md` (ISO date without hour)
|
|
|
|
**Build the checkout with this structure:**
|
|
|
|
```
|
|
# Weekly Review: [Date Range]
|
|
|
|
## Objectives
|
|
- List 2-3 high-level goals for the week based on the main themes of work
|
|
|
|
****Major Achievements****
|
|
- Bullet points of concrete deliverables, grouped by theme
|
|
- Focus on shipped features, solved problems, infrastructure built
|
|
|
|
****Code Activity****
|
|
- Stats line: X commits across Y repositories, Z PRs total (N merged, M open)
|
|
- **New Repositories**: `[name](url)` - brief description
|
|
- **Pull Requests Merged**: `[#N Title](url)` - one per line with descriptive title
|
|
- **Pull Requests Opened (not merged)**: `[#N](url)` - include status if known (approved, draft, etc.)
|
|
|
|
****Team Interactions****
|
|
- **Meeting Type (Nx)**: Brief description of purpose/outcome
|
|
With: Key participants
|
|
- **Notable conversations**: Date, participants, main subject discussed
|
|
```
|
|
|
|
**Rules:**
|
|
- Use `****Title****` format for section headers (not ##)
|
|
- All PRs and repositories must be markdown links `[name](url)`
|
|
- List merged PRs first, then open/unmerged ones
|
|
- Only include meaningful interactions (skip routine standups unless notable decisions made)
|
|
- No "who am I" header, no summary section at the end
|
|
- Focus on outcomes and business value, not just activity volume
|