Skip to content
UsecaseBoard
← All use cases
dev.toCodebase Exploration

Investigate an unfamiliar repository with locally cited answers

At a glance

Joy's RepoSeance inspects a local Git repository, explains selected evidence with Gemma and exports a Markdown report. This workflow is listed under Codebase Exploration, Local AI, Evidence Review.

Agents / tools
RepoSeance, Gemma 4 E2B, Ollama, Git

SourceBuilding a tool for these workflows? See weekly rates.

What they did

1) On Windows, install Git and Ollama, keep Ollama running, and pull `gemma4:e2b`. Download and extract the RepoSeance v1.0.0 Windows package from `Joyy-dev/reposeance`; open `reposeance.exe`. 2) Wait for its readiness check to confirm the local model connection, then select a local Git repository. The app captures a bounded selection of tracked files and commit records. 3) Generate the analysis report and inspect the captured excerpts behind findings. Ask a specific follow-up about those files, such as which dependencies are declared in `pubspec.yaml`. 4) Open the evidence IDs in the answer and compare each claim with the captured text. Treat an insufficient-evidence response as unresolved. 5) Export the Markdown report, optionally with the Q&A, for continued investigation.

How it went

The recorded self-analysis took 136.6 seconds. A separate synthetic fixture test correctly listed three declared dependencies and refused to infer an undocumented database-choice rationale.

Worth knowing

It cannot execute or repair the inspected project. Its partial snapshot and citations still require human interpretation.

Save ideas in this browser. Upvotes count across the board.

Prompt excerpt

No prompt excerpt was provided by the source.

Sponsored

CodeBuddy

Tencent Cloud AI coding assistant for IDE and CLI.

Try CodeBuddy ↗
Explore all →