How kunal-bhadra/git-insight works
Project type and purpose
• GitInsight is a full-stack, monolithic web application built with Spring Boot (Java) on the backend and Thymeleaf/Bootstrap/HTMX for the frontend.
• Its goal is to fetch a user’s recent GitHub activity, produce a “Quick Summary” of event counts, and generate a deeper, AI-powered “Smart Summary” via calls to a large language model (Gemini).
File structure
• Top-level:
• pom.xml — Maven build and dependency management
• src/main/java/dev/kunalb/gitinsight
– git package: GitHttpClient, GitInsight, GitSummaryGenerator, domain classes (RepoActivity, GitUser)
– llm package: LlmHttpClient, LlmInsight, LlmParser, persona definitions, PromptStore
– web package: ServerController (Spring MVC entry point)
• src/main/resources
– application.properties — config for API keys and ports
– templates (Thymeleaf): homepage.html, summary.html, layout.html
– public/img/site.webmanifest — static assets
• Test directory contains basic AppTest.
README
• Confirms tech stack: Spring Boot, Maven, Thymeleaf, HTMX, Bootstrap, Gemini API.
• Describes two main features: Quick Summary (event aggregation) and Smart Summary (LLM-driven feedback via personas).
• Shows external dependencies: GitHub API and Gemini API.
Main components
a. Frontend (Client Browser)
• Thymeleaf templates rendered by Spring
• Bootstrap/HTMX for styling and minimal JS interactions
b. Backend (Spring Boot Application)
• Controller layer: ServerController
• Service layer:
– GitInsight & GitHttpClient → GitHub REST API
– GitSummaryGenerator & GitSummaryCleaner → build quick summaries
– LlmInsight & LlmHttpClient → Gemini REST API
– LlmParser & PromptStore → process AI responses
• Domain/in-memory store: models (GitUser, RepoActivity) aggregated at runtime
• Configuration: application.properties, environment variables for API keys
c. External services
• GitHub REST API (for user events)
• Gemini (LLM) API (for smart analysis)
Relationships and data flows
1. Browser → HTTP GET “/” or “/summary” on ServerController
2. ServerController invokes GitInsight:
• GitHttpClient calls GitHub API → raw events
• GitSummaryGenerator cleans/aggregates data → Quick Summary
3. For Smart Summary:
• LlmInsight builds prompt via PromptStore → LlmHttpClient calls Gemini API
• LlmParser processes LLM response → Smart Summary
4. Consolidated model is passed back to Thymeleaf template → rendered HTML
5. Browser displays summary; HTMX may drive partial updates
Architectural patterns and design principles
• MVC (Model–View–Controller)
• Layered architecture: Controller → Service → HTTP Clients → External APIs
• Single-module monolith (no separate microservices)
• In-memory data aggregation for simplicity (no persistent database)
Detail
• Both Quick and Smart Summary flows.
• Critical configuration points (env vars, application.properties).
• If desired, note that persistence is in-memory (no DB node).