Daily Standup

# Daily Standup

Generate a clean three-line standup update from yesterday's commits, PRs,
or notes.

## When to use

Use this skill when the user:
- Pastes `git log --since=yesterday` output
- Pastes a list of merged PRs
- Lists what they worked on yesterday and what's planned today
- Asks "what should I say in standup?"

## Inputs

One of:
- A list of commit subjects or PR titles
- A free-form bullet list of yesterday's work
- A combination + an optional planned-for-today note

Optional:
- `blocker` — explicit blocker text. If absent and the user didn't
  mention a blocker, leave it as "None".

## Output format

Exactly three lines. No headings, no bullets per line, no preamble.

```
Yesterday: <what shipped or progressed, comma-separated, ≤ 100 chars>
Today: <what's planned, comma-separated, ≤ 100 chars>
Blockers: <None | one specific blocker>
```

## Process

1. Take the input. If it's commits/PRs:
   - De-duplicate by stripping conventional-commit prefixes (`feat:`,
     `fix:`).
   - Cluster related commits ("WIP" + "more WIP" + "finalize" = one item).
   - Keep at most 3–4 things on the Yesterday line. If there are more,
     summarize ("various skill-marketplace tweaks").
2. The Yesterday line should be in past tense, third-person-ish. Say
   "shipped X" or "wrapped Y", not "I did X".
3. The Today line should be specific and time-boxed. "Working on auth"
   is bad. "Adding rate limit to /api/login + tests" is good.
4. The Blockers line should name a person/team/system if there is one.
   "Blocked on Marcus for code review" beats "Blocked on review".

## Examples

**Input (commits):**
```
feat(skills): add import endpoint
test(skills): add 12 tests for import
fix(api): handle empty body
chore: bump dependencies
```

**Output:**
```
Yesterday: Shipped /api/skills/import + 12 tests, fixed empty-body bug, dep bumps
Today: Wiring import endpoint into the dashboard UI, then doc updates
Blockers: None
```

**Input (free-form):**
- finished auth refactor
- code review still open
- today: start on rate limit
- waiting on infra to provision the new postgres

**Output:**
```
Yesterday: Finished auth refactor (PR up for review)
Today: Starting on the rate-limit work for /api/skills/import
Blockers: Infra team — new Postgres still being provisioned
```

## Hard rules

- Three lines. Always. Not two, not four.
- Each line ≤ 100 characters. If the user has more to say, they should
  say it after standup, not in standup.
- Never include filler ("Hey team!", "Just wanted to update…").
- Never lie about progress. If yesterday was "stuck on the same bug",
  say that — that's the most useful standup update there is.
- "Blockers: None" is honest and fine. Don't manufacture a fake blocker.