At LovingSomeCode (LSC), every piece of work is meant to end up in our build log: what we built, on which project, when, and what we learned. It's our knowledge base, and it's where most of our content and case studies begin.

The problem: a log that depended on my memory

The catch is that it only got written when I remembered to ask Claude to update it after a session. With 20+ projects on the go, I forgot. A lot. Our most recent gap on one project was over 2 weeks long.

So we used Claude Code to take it off my plate.

How the nightly build log works

Everything the log needs already exists. Every change leaves a git commit, and every Claude Code session leaves a record of what we asked for, what we tried and why we chose what we did.

Now, every night at 10 pm, a small job gathers the day's commits and sessions from every project. Claude reads through them and writes one Notion entry per project, in the same style as our past entries.

The rules we gave it

It only writes what the work shows. Unfinished work is "in progress", never "shipped".
It never misses a night. Each run picks up where the last one stopped.
It never touches the code. It only reads.

Setting it up: 23 projects in one home

First, some housekeeping: we brought all 23 projects into one home, including a live app with real users. Everything was backed up and checked file by file, and nothing was pushed or deleted along the way.

Running every night

It's been running every night since we switched it on, and every run has gone smoothly. The build log keeps up with us now, not the other way round.

Most teams have a job like this: important, repetitive and easy to forget. We can build workflows like this for you too. Let's talk: lovingsomecode@gmail.com