← work log

26/10/2026 → 29/10/2026 · 24 commits

Shiplog

A self-hosted work diary that writes itself from your git commits and Claude Code sessions.

Role
Product, design and review by me; code mostly by Claude Code
Built
26–29 October 2026, 24 commits
Stack
Laravel 13, PHP 8.4, MySQL 8.4, Bootstrap 5.3, Pest
Status
Private for now; a public release is planned
Client portal

Orders (Checkout)

Stop charging the delivery fee twice on split orders.

commit 3f9c2ab

The problem

I tried keeping a work log by hand, and it never lasted more than a week. Meanwhile the real record was already there, in my commits and Claude Code sessions, spread over two client systems. Shiplog turns that record into the diary I never kept.

How it works

  1. You ask Claude Code to "update my board".
  2. The shiplog-update skill reads the commits and sessions since the last update. It writes one short card per project per day into a shiplog/v1 file.
  3. Shiplog checks the file and imports it.
  4. The board shows days down and projects across. Each card opens to the commits and sessions behind it.
git log --oneline
81148a9Skill (Update): write each card module first, the way commit subjects name the work
e99b19eSkill (Update): leave stashes and backup branches out of a lane's commits
438b9f4Skill (Update): read commits only from folders that are their own repository
personal

Skill (Update)

Cards lead with the module, the way commit subjects do.

81148a9e99b19e438b9f4
Three commits become one card.

Decisions worth a look

  • Imports only add or overwrite, and never half-load. Each card in a file adds the card for its day and project, or overwrites the one already there; cards the file doesn't mention are never touched. If anything in it is wrong, nothing is written and every problem is listed at once.
  • The documentation is a test. The README's JSON example is the importer's test fixture, and a test keeps the two identical. The documented format can't drift from what the code accepts.
  • No card without a source. The skill is asked to write only what the records show, and the importer enforces the part code can check: a card with no commit hash or session ID behind it is refused.
  • Demo mode can't touch a real diary. One setting serves only the read-only board, with no sign-in or upload routes registered at all. The demo seeder refuses to run outside demo mode, and a test starts the app a second time in demo mode to prove it.

The design

The first version looked like a stock admin template. I redesigned it after Power BI and Microsoft Fabric: a dark command bar with jump-to-card search, figures and charts for the last 30 days, and the diary as a grid. I measured the colours for contrast (white text on the buttons is 5.38:1). The motion follows a short set of rules: custom ease-out curves, nothing over 300ms, and fades only under reduced motion.

The Shiplog board with demo mode's invented data: figures and charts for the last 30 days, then the diary, days down and lanes across
The board, filled with demo mode's invented data.

By the numbers

170 cardsacross 74 working days in my own diary, going back to 2 August 2026. Most of them were filled in after the fact from commit history.
134 testsand 478 assertions, running in 6.8 seconds.
24 commitsbetween 26 and 29 October 2026.

Measured 2 November 2026.

Limits and what's next

  • Claude Code deletes session transcripts after 30 days by default, so older days are built from commits alone.
  • Next, I'd have the skill save a short summary of each session when it ends, so older cards no longer depend on transcripts that Claude Code deletes after 30 days.