GitHub Morning Brief

Generate a compact, action-first morning brief from GitHub signals.

Inputs to collect first

• owner/repo (required)
• org project number (optional but recommended)
• horizon: last 24h (default)
• optional extra risk repo(s) for security alerts

If something is missing, ask one short question, then continue.

Workflow

1. Pull ask-signals from notifications: mention, review_requested, assign.
2. Pull open PR list and identify:

• merge candidates (approved + clean + checks green)
• fast-review candidates (recent activity, clean mergeability)
• blocked PRs (conflicts/failing checks)

1. Pull project board snapshot (status buckets and counts).
2. Pull CI and security risk signals.
3. Produce a short start-of-day plan (1–3 concrete actions with links).

Use exact command patterns from references/commands.md.

Output format (recommended)

• Short briefing paragraph (what matters right now)
• Ask-signals section with links
• Project/PR/CI snapshot
• Risks section
• 1–3 concrete next actions (priority order)
• Optional: draft review text for one selected PR

Guardrails

• Keep tone practical and concise.
• Include direct links for every PR/issue/run mentioned.
• Do not post comments/reviews/merges automatically unless user explicitly asks.
• If data is partial (permissions/API failure), state it clearly and still provide best-effort priorities.