Rebundle
/daily-review
Skill

Daily Review

Cierra el día en 5 minutos: qué hiciste, qué quedó pendiente y propuesta de foco para mañana.

SKILL.md
---
name: daily-review
description: At the end of the day, cross-reference the user's calendar, commits, sent messages, and journal entries from today. Produce a structured review (Done / Pending / Postponed) and propose three focuses for tomorrow. Detect patterns of recurring postponement and surface them gently. Run in under 5 minutes of compute time.
---

Daily Review

The end-of-day cousin of a morning brief. Helps the user decompress, see the day clearly, and walk into tomorrow with a plan instead of anxiety.

When to use this skill

  • The user is closing their laptop for the day.
  • Before dinner / family time / detaching.
  • On Sunday evening for a weekly review variant.

Sources to read

In order of priority:

  1. Calendar — meetings attended today (skip declined / canceled).
  2. Commits and PRs — what shipped or attempted to ship.
  3. Sent messages — Slack and email outbound (only headers, not full content).
  4. Journal / notes — anything tagged today.
  5. Todo list — items marked done today and items still open.

If a source is unavailable, skip it and note it in the output.

Structure

Hecho hoy

Concrete outcomes. Format: bullet, verb-first, past tense. "Cerré contrato con Banesco" not "Tuve reunión con Banesco".

Pendiente

Items still open from today's commitments. Source from:

  • Calendar items marked as needing follow-up.
  • Tasks still in todo with today's date.
  • Sent messages that asked a question and got no reply yet.

Postponed (3+ veces)

Items that have been moved forward at least 3 times. Cross-reference the journal/todo history. Surface them as a gentle note, not a guilt trip.

Foco mañana

Exactly 3 priorities. Pick from:

  1. The most blocked Pendiente.
  2. The most expensive Postponed.
  3. One thing the user explicitly said matters this week (read context file).

If the user has 4+ urgent things, force the choice. Three is the cap.

Pattern detection

After 7 daily reviews, surface patterns:

  • "Postponed 'migración Postgres' 5 weeks running."
  • "Friday commits average 0.5 vs Tuesday 4.2 — Fridays are admin days for you, not shipping days."
  • "Slipped 'Banesco' commitment by 2 business days, accepted by the customer but worth tracking."

Frame patterns as observations, not judgments.

Output format

Daily review · {weekday} {DD} de {month}

✅ Hecho hoy
- ...

⏳ Pendiente
- ...

🔄 Postponed (3+ veces)
- ...

🎯 Foco mañana
1. ...
2. ...
3. ...

Patrón detectado: {observation}

Constraints

  • Never read full message bodies. Headers and metadata only.
  • Never include sensitive content (auth, private DMs, financial details) in the output.
  • If the user's day was empty (vacation, sick), skip the review and ask if they want to log a reason.