juharris/daily-report

Check for unanswered messages from Geekbot in the DM channel and answer them.

Step 1: Read the conversation and gather work data in parallel

Do these in parallel:

1. Read the last 3 messages from Geekbot DM channel to find the most recent unanswered question.
2. Gather today's work data (PRs, issues created, Slack activity, calendar meetings) using the /weekly-summary skill approach, but scoped to today only.

When querying gh for today's PRs, compute the date dynamically with date +%Y-%m-%d (macOS) instead of hardcoding a date string. For example:

gh pr list --author=@me --state=all --json title,url,state,mergedAt,createdAt,number --search "created:>=$(date +%Y-%m-%d)"

Also fetch issues the user filed today (across all repos, not just the current one) so they appear in the summary:

gh search issues --author=@me --created=">=$(date +%Y-%m-%d)" --json title,url,state,createdAt,number,repository --limit 30

Step 2: Determine which question is unanswered

Analyze the conversation to find the FIRST Geekbot question that has NO user reply after it:

• Look for non-Geekbot messages between Geekbot's questions to identify already-answered questions.
• If Geekbot asks another question after an interactive mood question, treat the mood question as already answered. Slack history does not always expose the selected interactive button value, but Geekbot advancing to the next question proves the user completed it.
• Only respond to the first unanswered question.
• Do NOT re-answer questions the user already responded to.

Step 3: Answer the unanswered question

"How did you feel today?" or "How are you feeling today?" — SKIP, do not answer

This question uses interactive buttons in Slack. Tell the user to pick their answer in Slack, then re-run the skill. Do NOT send a text message for this question.

"What did you work on today?" or "What will you work on today?" — Answer with work summary

Use the work data gathered in Step 1 to compose a summary.

• Do not use Markdown formatting — use plain text with typical Slack formatting (bullets with •).
• Put the most impactful highlights first at the top.
• Include: merged PRs, open PRs, issues filed today (across all repos), notable PR reviews, important Slack discussions, notable meetings.
• Only mention issues filed today when at least one issue was filed. Do not add a "no issues filed today" bullet when there were none.
• When linking to PRs or issues in the draft, use Slack's native <url|label> mrkdwn format (see the /messaging-etiquette skill). Plain URLs do not reliably auto-link inside indented sub-bullets in Slack drafts.
• Emphasize WHY the work matters, not just what was done.
• Follow the discretion guidance from the /weekly-summary skill when drawing from private sources. Minimize names — only name someone when attribution is load-bearing (they own the work, or credit is due). Do not name people for routine reviews, DMs, or meeting attendance, and never attach a name to anything that could read as criticism or surface something private about them (calendars, interviews, hiring, personal behavior) — drop the name, the detail, or the whole bullet.

"Is there anything blocking your progress?" — Answer with just a dash

Send: -

"Thanks Justin! You are the best!" — STOP, do not respond

This is Geekbot confirming the report is published. Do not reply.

Step 4: Wait and check for follow-up questions

After sending a response, wait 10 seconds using sleep 10 via Bash, then check the channel again for the next question. Repeat Steps 2-4 until Geekbot says thanks or there are no more unanswered questions.