Answering “what did you do yesterday” at standup

When standup reaches you and someone asks what you did yesterday, you know the afternoon was busy, but the filenames, the errors, and the directories you were halfway through have already been covered by this morning’s compile, new messages, and the editor you just opened. Of the three standup questions, this is the one most likely to come out empty. When you rely only on memory, what you finished, what you asked, and what you started often blend into one sentence. You can open Hina first, look at yesterday’s Trail, find the stretches that have names, and then use local commits to check what the repository kept.
Yesterday afternoon gets covered by this morning
Window titles and page paths have to be turned on in privacy settings before you can find document names and paths. What is useful in standup is usually a document title, a project directory, or a page path you still recognize. A named stretch makes it easier for people to hear where you stopped than saying only that you wrote a lot yesterday.
Check the Trail, then local commits
Before the meeting, open Hina, step back one day with Previous, and look at yesterday’s Trail. First find the afternoon block where the editor stayed continuously in the blog repository, or a document path you still recognize, then open that day’s Daily report, look at the local commits in it, and check what the repository actually kept. Hina’s own command line shows the same material. --overview yesterday shows the apps you used yesterday and how long, and --daily yesterday prints the same daily report, so you do not have to piece things together from whatever little you remember this morning.
A matching commit is a result already left in the repository. A matching uncommitted change is a modification still in the working tree that has not been written into a commit. You can mention either one in standup. What you asked AI appears in the daily report only when you enable it separately, and it is off by default. It helps you remember the error or the document you wanted to look up at the time. Even when a question sits very close in time to a commit, that does not mean the question was already finished.
Say finished, asked, and started separately
When it is your turn, keep finished, asked, and started apart. Finished means naming the place already visible in the repository. Asked stops at the question in the daily report. Started only means the Trail has a stretch you can name, and the changes in the working tree have not become a commit. That is clearer than folding everything into one sentence that you spent yesterday on that feature.
Here are three sentences you could say in standup. The navigation style in the blog repository is already committed, and on a narrow screen the header no longer covers the title. That one counts as finished. In the client’s website repository the export button was covered, you asked AI whether it was a style override, and the page has not been changed. That one counts as asked. The pricing page copy stayed in the editor all afternoon, and the file is still in the working tree. That one counts as started.
1 a.m. still counts as the previous day
In Hina a day runs from 4:00 a.m. to 4:00 a.m. the next day. A change you were still writing, with the editor still open at 1:00 a.m., still counts as the previous day, not a new day that starts after you wake up and see the first email. If morning standup is about yesterday, whether you open yesterday’s daily report in Hina or use --daily yesterday, commits left in the middle of the night fall on yesterday. If you describe the 1:00 a.m. work as something you did only today, the Trail and the day you say will diverge. Only editing, compiles, and commits that start after 4:00 a.m. count toward the new day.
If Hina was not running for a whole stretch yesterday, that stretch is blank on the Trail, and the filenames and stretches from it will not match. In standup, say plainly that you cannot remember that stretch. If you do remember, you can fill in the specific thing yourself, such as the interface notes you were still editing after midnight. If you do not remember, leave it blank. The editor still open this morning cannot fill that gap.