Built this because I was sick of having 15 versions of my resume with no idea which one I sent where

Built a dumb little tool for myself last weekend and figured I'd share it in case anyone else has the same annoying problem.
Every time I applied to a job, I'd end up with 6 versions of my resume floating around — "resume_final.pdf," "resume_final_v2.pdf," "resume_ACTUALLY_final.pdf," you know the drill. And I'd forget which one had the tailored bullet points for which company.
So I put together Overmind. It's basically just LaTeX + git branches + a couple of Cursor agent skills, nothing fancy:

→ Keep one clean base resume on master
→ Spin up a branch per job description (jd-company-role)
→ Ask the agent to pull keywords from the JD and rewrite bullets for ATS matching, while keeping the formatting parser-safe
→ Build gives you a proper PDF, and your whole history is just... version controlled, like actual work should be

Nothing groundbreaking, honestly. I just got tired of guessing which resume I sent where, and version control already solved this problem for code twenty years ago — I don't know why I wasn't using it for my resume too.
It's open source, still rough around the edges, and I'd genuinely love feedback if you try it or have ideas for what's missing.
Repo's here if you want to poke around:

venkatmidhunmareedu / overmind

The open-source standard for AI-assisted resume creation. Leveraging modern editors to bridge the gap between structured LaTeX typesetting and intelligent content generation.

Overmind

Overmind is a LaTeX-based resume workflow for creating a clean base resume and generating role-specific variants quickly. It is designed for iterative editing in Cursor/VS Code, ATS-oriented tuning, and reproducible PDF output (resume.pdf) from source files in this repository.

The recommended workflow is:

• maintain a stable, generic base resume on master
• create job-description-specific branches for tailored versions
• keep each branch focused on one target role/company so updates are easy to track and reuse

Development Guide :

1. Fork this repository to your own GitHub account (recommended) so you own your resume history and customizations.
2. Clone your fork locally
   • git clone https://github.com/<your-username>/overmind.git
3. Keep your base resume on master, then create one branch per job description
   • git checkout -b jd-<company>-<role>
   • Example: git checkout -b jd-acme-backend-engineer
4. Install the necessary extensions and packages for your operating system.
5. Build the project using
   • Press Ctrl + shift + p to open the control…

View on GitHub

I already got mine. Check it out here :

venkatmidhunmareedu / resume

Latex Resume

Development Guide :

1. Clone the repository
   • git clone https://github.com/venkatmidhunmareedu/resume.git
2. Install the necessary extensions and packages for your operating system.
3. Build the project using
   • Press Ctrl + shift + p to open the control panel and search for LaTex Workshop: Build LaTex Project
   • Or Simply Press Ctrl + Shift + B (which is a preset, see the settings yourself)
4. Go thorough the resume.pdf file. (The code build and saves the pdf on save that looks like live reload)

Steps to preview the resume in VS Code or any other VS Code Fork.

1. Find LaTex Workshop extension and install it. (https://marketplace.cursorapi.com/items/?itemName=James-Yu.latex-workshop)
2. If your platform is:

• Linux
  • sudo apt install texlive-latex-base texlive-fonts-recommended latexmk texlive-latex-extra
  • (Warning) This command downloads packages upto 600MB of data.
• Windows:
  • You have install Perl from https://strawberryperl.com/
  • if it's not installed already, open the MikTeX Package Manager and install the latexmk package.
• Mac
  • It’s…

View on GitHub