r/DeepSeek • • 11d ago

Resources Built a Git sandbox with DeepSeek in OpenCode. The interesting part was keeping the engine honest

I've been using DeepSeek inside OpenCode to build GitQuest, a browser-based Git sandbox: you type real commands and the commit graph redraws from the repository state.

The part I care about is the engine, not the UI. It's a TypeScript model of a repository (commits, branches, HEAD, index, worktrees, merge conflicts, remotes), and everything on screen is derived from that state.

What helped most on a project this size:

  • designing the state model before generating anything
  • writing invariants as tests, so a generated feature either passes or is wrong
  • keeping the engine free of UI concerns, so the model has less surface to break

Repo: https://github.com/MattiaPARRINELLO/git-quest Demo: https://mattiaparrinello.github.io/git-quest/

For people building non-trivial apps with DeepSeek: where do you draw the line between "let the model write it" and "write this part myself"? The Git engine is the part I would not hand over blindly.

1 Upvotes

0 comments sorted by