Explain repo evolution using git log history

Marius
Marius Colacioiu • @colmarius
 8mo ago
main
Medium
Unlisted
Review the whole git log of this project, read the comments, check the diff roughly, and then use it as input together with the walkthrough skill to explain the evolution of this repo. The goal is to onboard a dev to understand the history of building this repo, focus on main important parts, details only if relevant.

MobCrew Evolution Summary

MobCrew is a native macOS mob programming timer built entirely through an AI-assisted workflow using the Ralph autonomous agent.

Key Development Phases

Phase Commits Description
1. Foundation b69ad49 → 2ca2f90 Agent setup, research (Ghostty patterns, Elm→Swift porting), PRD creation
2. Scaffolding a8c7e67 → 9fc46c1 PLAN-000: Xcode project, folder structure, core models (Mobster/Roster/TimerState), tests
3. Core Features d1bef26 → eacf655 PLAN-001: TimerEngine, FloatingTimer (NSPanel), MenuBar, RosterView, PersistenceService
4. Polish 4788e33 → 6acd661 UI improvements, breaks, notifications, global hotkeys, settings, release automation, landing page

Architecture Highlights

  • SwiftUI + AppKit hybrid: MenuBarExtra with NSPanel floating window
  • Feature-based folders: Features/{Break,FloatingTimer,MenuBar,Roster,Settings}
  • PRD → Plan → Ralph workflow: Research informs PRDs, plans are executed autonomously in 5-task batches

View interactive walkthrough: https://ampcode.com/docs/T-019c1ba0-b486-75bc-887b-14ddd6684695

Can you use such diagram for the repo documentation? Also feel free to add link to the Amp Thread on main README.md mentioning project was built with Amp (link to ampcode.com): https://ampcode.com/threads/T-019c1ba0-b486-75bc-887b-14ddd6684695

Done! Added to README.md:

  1. Amp attribution at the top with link to the development thread
  2. Project Evolution diagram (Mermaid) with a summary table showing the 4 phases

GitHub will render the Mermaid diagram natively. The interactive version with clickable nodes is available at the Amp thread link.

Lets add a note is costed ~60$ in tokens to build.
Edited 1 file (+1 -1)

Done. Added the ~$60 cost note to the Amp attribution line.