Catchup

# Document Analysis Patterns

## Meeting Notes Analysis

When catching up on meeting notes or discussions:

**Context Establishment:**
- Identify date range: "Last meeting I attended was [date]"
- Note participants involved
- Identify meeting series or project name

**Delta Capture:**
- List topics discussed (agenda items)
- Enumerate decisions made
- Identify action items assigned
- Note open questions or blocked items

**Insight Extraction:**
- What changed since last meeting?
- What decisions affect ongoing work?
- What consensus emerged on contentious topics?
- What new information affects project direction?

## Sprint/Ticket Catchup Patterns

For Jira, GitHub Issues, or similar tracking systems:

**Context:**
- Last sprint/milestone reviewed
- Current sprint/milestone
- Team velocity or capacity changes

**Delta:**
- Tickets completed since baseline
- Tickets in progress
- New tickets added to backlog
- Priority shifts or re-ordering

**Insights:**
- Velocity trends (ahead/behind schedule?)
- Risk indicators (blocked tickets, dependencies)
- Scope changes (new requirements, deferred items)
- Team capacity changes

## Document Revision Tracking

When reviewing evolving documents (specs, designs, RFCs):

**Context:**
- Last version reviewed (version number, date, or commit)
- Current version
- Document type and audience

**Delta:**
- Sections added, modified, or removed
- Comments or review feedback incorporated
- Status changes (draft → review → approved)

**Insights:**
- Requirements changes and rationale
- Design decisions made or reversed
- Unresolved discussions or open questions
- Approval status and blockers

## Generic Document Delta Patterns

**Efficient Enumeration:**
- Focus on substantive changes (ignore typos, formatting)
- Identify authors/contributors to understand perspective
- Note timestamp for context
- Track references to external decisions or dependencies

**Token Conservation:**
- Summarize content rather than quoting verbatim
- Reference section headings and key points
- List decisions/actions rather than narrative
- Use bullet points for scanning efficiency


---
name: git-catchup-patterns
description: Git-specific commands and patterns for catchup analysis
parent_skill: imbue:catchup
category: technical-patterns
tags: [git, version-control, delta-capture]
estimated_tokens: 400
---

# Git Catchup Patterns

## Git Context Establishment

Use these commands to establish git repository context:

```bash
pwd                                                 # Show current directory
git status -sb | head -n 1                          # Show current branch and status
git rev-parse --abbrev-ref --symbolic-full-name @{u}  # Show the upstream branch, if one is being tracked
```

These help answer:
- Where am I working?
- What branch am I on?
- Is this branch tracking a remote?

## Git Delta Capture

Efficiently capture changes between states:

```bash
git diff --stat ${BASE}...HEAD                      # Show summary statistics
git diff --name-only ${BASE}...HEAD                 # List changed files
git log --oneline ${BASE}...HEAD                    # Show commit history
```

**Key Patterns:**
- Use `--stat` for high-level overview (files changed, insertions/deletions)
- Use `--name-only` for enumeration without content
- Use `...` three-dot syntax to show changes on current branch since divergence

## Semantic Delta Capture (sem)

When sem is available (see `leyline:sem-integration`),
enhance delta capture with entity-level diffs:

```bash
# Entity-level change summary across commits
sem diff --format json ${BASE}...HEAD

# Track a specific entity's evolution
sem log <entity-name>
```

> **Note:** sem may not support three-dot (`...`) range
> syntax directly. If `sem diff` fails