SlothLog: Why I Built an Offline, AI-Powered Timesheet Generator for Lazy Developers

Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady Submission 🦥

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady

Every Friday afternoon at 4:30 PM, an invisible cloud of collective dread descends upon software engineering teams: logging our hours into Jira, Azure DevOps, or corporate time trackers.

You open your tracking tool, stare at a blank grid of empty days, and begin the painful archaeological dig through your week:

The result? Developers either spend 45 minutes of precious Friday time reconstructing history, or they guess haphazardly, slapping 8.0h - General Development across every day of the week.

I wanted to be completely, unapologetically lazy.

So I built SlothLog (🦥): an offline, privacy-first developer utility that inspects your local git commits across multiple repositories, clusters activity by ticket identifier, estimates work session duration, and synthesizes executive-ready timesheet summaries using Google Gemma 2 2B running locally via Ollama.

Here is SlothLog in action running locally with its utilitarian dark dashboard:

The web dashboard features an interactive date selector, hour stepper ( + / - 0.25h), tracked repository manager, and single-click copy buttons with instant toast confirmations:

+---------------------------------------------------------------------------------------+ | 🦥 SlothLog Offline AI Timesheets for Lazy Developers [Gemma 2 2B] [Sentry Active]| +---------------------------------------------------------------------------------------+ | [ Total Logged: 7.00 h ] [ Clustered Tickets: 3 ] [ Effort Saved: ~45 mins ] | +---------------------------------------------------------------------------------------+ | [AB#4920] billing-service [-] 3.25h [+] | | "Refactored invoice calculation engine, added VAT reverse charge support for European | | B2B invoices, and implemented idempotency tests." | | [ 3 underlying commits ] | | [📋 Copy for Jira / DevOps] [📄 Copy Summary] | +---------------------------------------------------------------------------------------+ | [PROJ-104] portal-frontend [-] 2.50h [+] | | "Implemented OAuth2 PKCE login flow callback and added refresh token rotation." | | [📋 Copy for Jira / DevOps] [📄 Copy Summary] | +---------------------------------------------------------------------------------------+ Enter fullscreen mode Exit fullscreen mode 2. Standalone CLI Flow If you prefer staying in the terminal:

$ python cli.py scan --date 2026-10-20 Scanning 2 repositories for date: 2026-10-20... Generated Timesheet: Date | Repo | Ticket | Hours | Summary ----------- +-----------------+---------------------+-------+------------------------------------------------------------ 2026-10-20 | billing-service | AB#4920 | 3.25h | Refactored invoice calculation engine, added VAT reverse... 2026-10-20 | portal-frontend | PROJ-104 | 2.50h | Implemented OAuth2 PKCE login flow callback... 2026-10-20 | billing-service | General Maintenance | 1.25h | Upgraded dependencies, cleaned up unused imports... Total Hours: 7.00h Enter fullscreen mode Exit fullscreen mode You can also export to standard CSV with python cli.py export -o timesheet.csv for HR and payroll imports.

Turn your git commits into honest, sensible timesheets — without leaking company code to the cloud.

Every Friday at 4:30 PM, the same ritual happens across engineering teams:

Most of us waste 30 to 45 minutes every week doing this archaeological reconstruction. And while modern AI tools can summarize text, pasting internal commit messages and proprietary code into third-party cloud APIs is a fast track to an unpleasant chat with Infosec.

SlothLog fixes this by staying completely local: