How to use Claude to build a Git history viewer
Git Lineage was built with Claude Code over six and a half months, with the author reviewing and manually testing every PR and remaining hands-on with performance and UX.
AddedBuilding, testing, debugging and maintaining software or infrastructure, with code review and checks before changes reach users.
424 use casesShowing 145–168
Preparing search…
Git Lineage was built with Claude Code over six and a half months, with the author reviewing and manually testing every PR and remaining hands-on with performance and UX.
AddedClaude Code hooks enforce a failing-test-first development loop, with Playwright checks retained in the codebase and manual testing and line-by-line review before merging.
AddedThe creator finished an inherited message board with Claude Code and describes version-checked payment activation, refunds, and substantial performance and security work.
AddedClaude Code reproduced a llm-gemini command error, fixed the unsupported media resolution issue, and ran tests; the author reviewed and manually verified the change.
AddedThe Backlog.md creator reported improving an agent coding workflow through project documentation, individual Markdown tasks, planning, and review before merging.
AddedCasperAI’s creator used Claude Code to generate about 80% of its TypeScript, including the MCP server and SQLite schema. The author retained architecture, debugging, documentation and edge-case testing.
AddedThe author described a Grok Bot merge gate requiring green repository CI followed by full-diff review from a separate agent. A 167-file PR was held for six fixes before merging.
AddedGrok Bot helped prepare and test companion-app changes across several platforms. The author reported five merged PRs and a Windows build break caught on real hardware after cloud CI missed it.
AddedThe author prototyped search intelligence with Claude and Claude Code, encountered excessive API consumption, then used SerpAPI and Lovable for a tool used daily.
AddedIn a reported demo, AURA investigated checkout 502s, traced them to a downstream memory leak, documented a fix through a human-gated GitHub call, and checked recovery.
Added AURARecall built Predict largely with Claude Code subagents, then shifted from a Figma MCP design workflow to a designer prompting iterations directly into code. The author reported an end-to-end working loop with rough edges.
AddedHawkDoc combines Lexical editing with React, collaborative-sync infrastructure, and Markdown, HTML, and PDF export. Its author credits Claude Code for early editor integrations and export development.
AddedA developer used Claude Code and Codex CLI to write svelte-check-rs, retaining architecture and real-codebase testing. The source reports cold, warm, and iterative speed improvements on a SvelteKit monorepo.
AddedIndexio indexes a codebase and serves Claude Code lookups through MCP, falling back to regex when needed. Its authors report reduced token use but identify symbol-heavy workflows as a limitation.
AddedChatML gives parallel Claude Code tasks separate Git worktrees, branches, and working directories. The team used the workflow for most of ChatML and reports merging over 750 generated pull requests.
AddedMaxxwell coordinates parallel Claude and Codex sessions through an orchestrator that monitors goal checklists and brings important decisions back to the user.
AddedWillison asked Claude Code for web to compile Gifsicle to WebAssembly and build a preview interface. The agent used Rodney to exercise the page and fix UI bugs during implementation.
AddedWillison wanted to optimize a phone recording before publishing it. He used Claude Code for web to build a browser tool around FFmpeg compiled to WebAssembly, with multiple output presets.
AddedWillison delegated a Moebius model port to Claude Code using local repositories and a research note. He tested the browser UI and returned errors while the agent iterated on ONNX and WebGPU support.
AddedSimon Willison gave Codex a specific defect in his Django blog: social preview descriptions exposed raw Markdown. Codex changed templates and added a passing test in a configured PostgreSQL environment.
AddedWillison published the Codex session used to build the Datasette project blog. The agent inspected the existing site, moved conflicting database routes and implemented blog behavior with local checks.
AddedWillison supplied an existing parser and an independent compatibility suite, reviewed an API plan, then let Codex implement a JavaScript port through repeated tests and commits.
AddedDodds used Cursor with GPT-5.4 to add lexical retrieval to his semantic search. Production blocking exposed an architectural flaw, so later agent work moved search into a unified Worker.
AddedDodds delegated an audio pipeline migration to Cursor. He rejected an initial design that preserved a separate service and used another agent run to make the sandbox part of the existing queue Worker.
Added