daily-report

You are an assistant that creates a Daily Report in a text-ready format for the Acme project — suitable for the daily stand-up (16:00 Vietnam / 10:00 Portugal) and the Slack daily update.

Purpose

At the end of the day, generate the content for the 4 sections of the Daily Report Slack form:

1. What did you do today? — list ticket + title (do NOT show progress %)
2. Hours — a per-task breakdown plus an estimated total (see "Hours estimation" below)
3. Self-testing video/screenshot — leave blank (you upload it yourself)
4. Relevant links — commits, MRs, Figma, Jira

Input

$ARGUMENTS — date (optional, default = today).

• No arg → today
• yesterday → yesterday
• 2026-04-27 → a specific date

Actions

STEP 1: Read the daily report file

DATE="${ARGUMENTS:-$(date +%Y-%m-%d)}"
if [ "$ARGUMENTS" = "yesterday" ]; then
    DATE=$(date -v-1d +%Y-%m-%d)
fi
REPORT_FILE="daily-reports/$DATE.md"

if [ ! -f "$REPORT_FILE" ]; then
    echo "ERROR: No report file at $REPORT_FILE"
    echo "There may be no commits on $DATE yet."
    exit 1
fi

STEP 2: Parse entries from the file

Read all entries in the file (each commit is one entry with the header ## [HH:MM] hash — subject).

Group by Jira ticket. For each ticket, list:

• Title (extracted from the commit subject)
• Branch
• Stats summary

STEP 3: Get additional MR/PR info from git

# List branches pushed during the day (associated with an MR)
git for-each-ref --sort=-committerdate --format='%(refname:short) %(committerdate:short)' refs/heads/ | grep "$DATE" | head -10

# Optional: query the GitLab API if there are MRs for the branches
# (skip if not needed — you can fill it in manually)

STEP 4: Estimate hours per task

Produce a per-task hours breakdown and a total.

Estimate by human effort — how long the work would take a developer doing it by hand. This is deliberately NOT wall-clock time and NOT agent execution time, both of which understate the real cost (parallel tool calls, no context-switching, no reading time).