<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Jiya Kapoor</title>
    <description>The latest articles on DEV Community by Jiya Kapoor (@jiya_kapoor_6be229ccc9c4a).</description>
    <link>https://dev.to/jiya_kapoor_6be229ccc9c4a</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3951076%2Ff0b1e3d2-d093-4942-8ca2-28727b39c77f.png</url>
      <title>DEV Community: Jiya Kapoor</title>
      <link>https://dev.to/jiya_kapoor_6be229ccc9c4a</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jiya_kapoor_6be229ccc9c4a"/>
    <language>en</language>
    <item>
      <title>From a Git Clone to an AI-Powered VCS That Understands Your Code</title>
      <dc:creator>Jiya Kapoor</dc:creator>
      <pubDate>Sun, 07 Jun 2026 06:59:44 +0000</pubDate>
      <link>https://dev.to/jiya_kapoor_6be229ccc9c4a/from-a-git-clone-to-an-ai-powered-vcs-that-understands-your-code-4556</link>
      <guid>https://dev.to/jiya_kapoor_6be229ccc9c4a/from-a-git-clone-to-an-ai-powered-vcs-that-understands-your-code-4556</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/github-2026-05-21"&gt;GitHub Finish-Up-A-Thon Challenge&lt;/a&gt;&lt;/em&gt;&lt;br&gt;
&lt;strong&gt;What I Built&lt;/strong&gt;&lt;br&gt;
PivotVCS — a full-stack AI-powered version control system built from scratch using Java, Spring Boot, React, and FastAPI. It started as a curiosity project — could I build my own Git-like system? But it grew into something much bigger: a developer tool that not only handles branching, commits, and merges but also understands your code through AI.&lt;br&gt;
PivotVCS lets developers commit files, switch branches, visualize commit history, and now — ask natural language questions about their own codebase. It feels personal because I built every layer of it, from the tree-based file versioning to the RAG pipeline that powers the copilot.&lt;br&gt;
Demo&lt;br&gt;
GitHub Repo Link&lt;br&gt;
BACKEND: &lt;a href="https://github.com/JiyaKapoor/Pivot-web" rel="noopener noreferrer"&gt;https://github.com/JiyaKapoor/Pivot-web&lt;/a&gt;&lt;br&gt;
FRONTEND: &lt;a href="https://github.com/JiyaKapoor/PivotFrontend" rel="noopener noreferrer"&gt;https://github.com/JiyaKapoor/PivotFrontend&lt;/a&gt;&lt;br&gt;
OLD REPO: &lt;a href="https://github.com/JiyaKapoor/pivot" rel="noopener noreferrer"&gt;https://github.com/JiyaKapoor/pivot&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Key features in action:&lt;br&gt;
Create branches, commit files, and visualize commit history in a GitHub-style UI&lt;br&gt;
Merge branches with an AI-powered safety analysis before merging&lt;br&gt;
Ask natural language questions about your codebase via the Pivot Copilot panel&lt;br&gt;
Automated code review and branch summarization triggered on every commit&lt;/p&gt;

&lt;p&gt;The Comeback Story&lt;br&gt;
When I first built PivotVCS, it was a functional but basic VCS:&lt;/p&gt;

&lt;p&gt;-Commit and file versioning&lt;br&gt;
-Branching and merging&lt;br&gt;
-Basic commit history UI&lt;/p&gt;

&lt;p&gt;It worked, but it was just another Git clone. Here's what I came back and added to finish it up properly:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Database layer for collaboration
Added a full persistence layer using PostgreSQL and Hibernate so multiple users can collaborate on the same repository, with optimistic locking on branch HEAD entities to handle concurrent commits safely.&lt;/li&gt;
&lt;li&gt;Multi-Agent AI Pipeline
Integrated a LangGraph multi-agent architecture that automatically triggers on every commit and runs three parallel agents — a code review agent, a branch summarization agent, and a merge safety analysis agent — persisting results per commit for historical querying.&lt;/li&gt;
&lt;li&gt;RAG-based Copilot
Built a full RAG pipeline that indexes repository files as semantic chunks using Mistral AI embeddings, stores them in Supabase pgvector, and powers a natural language chat interface embedded directly in the repo view. Developers can now ask questions like "How is authentication handled?" and get context-aware answers with source file attribution.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;My Experience with GitHub Copilot&lt;br&gt;
GitHub Copilot was genuinely useful throughout the finishing phase of this project. The most valuable moments were:&lt;/p&gt;

&lt;p&gt;Boilerplate acceleration — setting up DTOs, service layers, and REST controllers in Spring Boot is repetitive; Copilot handled the scaffolding so I could focus on the actual logic&lt;/p&gt;

&lt;p&gt;FastAPI and Python interop — switching context between Java and Python frequently, Copilot helped me stay consistent with naming conventions and Pydantic model structures&lt;/p&gt;

&lt;p&gt;Debugging assist — When I ran into bugs between the Spring Boot and FastAPI services, Copilot would suggest the fix &lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>githubchallenge</category>
    </item>
  </channel>
</rss>
