# TurtleShell: Let a Local Tortoise Turn Messy Git History into Standups

> Source: <https://dev.to/dakaufeeboii/turtleshell-let-a-local-tortoise-turn-messy-git-history-into-standups-38hk>
> Published: 2026-10-25 19:05:33+00:00

*This is a submission for the [Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady](https://dev.to/challenges/hacktoberfest-week3-2026-10-19)*

Standup time has a familiar ritual: open the terminal, scan a handful of commits called `wip`, `it works now`, and `fix typo`, then try to remember what the work actually meant.

I built **TurtleShell 🐢**, a local-first tool that inspects a Git repository and turns recent commit messages and filtered diff excerpts into two useful drafts:

The dashboard also compares raw commits with the generated summary and lets me copy the standup to Slack. When MongoDB Atlas is configured, TurtleShell saves generated updates for later search. The goal is to spend less time reconstructing yesterday and more time getting on with today.

TurtleShell runs locally. Start the backend and open `http://localhost:3456` to try the dashboard. There is no hosted demo or video at the moment.

The project is open source: [DaKaufeeBoii/turtle-shell on GitHub](https://github.com/DaKaufeeBoii/turtle-shell).

TurtleShell is a TypeScript app with an Express backend and a browser dashboard. Its workflow is:

The agent workflow uses **Mastra** for orchestration and Ollama for local inference. MongoDB and Sentry are optional integrations; without MongoDB configured, the app falls back to local JSON history.

To run it locally, install Node.js 20+, install Ollama, and pull the model:

```
ollama pull gemma2:9b
```

Then install and start the backend:

```
git clone https://github.com/DaKaufeeBoii/turtle-shell.git
cd turtle-shell/backend
npm install
npm run dev
```

Open `http://localhost:3456`. For terminal output, run `npm run sloth`.

Git history can reveal unreleased work, internal names, and implementation details. Running an open-weight model locally lets me summarize that context without sending it to a hosted model API. I can inspect the model workflow, change the prompts, and run the tool on my own machine.

Open tools also make the workflow adaptable: the model, repository filtering, memory store, and tracing can each be configured or replaced. That control matters for a tool whose input is a developer’s private working history.

Here’s the published DevRelay session behind the project: [Building TurtleShell: The Slow and Steady Git Janitor](https://dev.to/agent_sessions/building-turtleshell-the-slow-and-steady-git-janitor-liefdr).

The payoff is a ready-to-edit standup and changelog instead of manually translating commit fragments into a coherent update. I haven’t measured time saved across repeated use yet, so I’m keeping the claim qualitative: TurtleShell cuts down the daily context-reconstruction work and leaves the final wording in my hands.

Built for Hacktoberfest 2026 Week 3: Slow and Steady.