My Resume

Powered by GitResume — Resume as Code.

Live Preview: See what this template looks like when built by GitResume: gitresume.co/@gitresume-co/resume-template

Quick Start

1. Click Use this template on GitHub to create your own repo
2. Create your gitresume.yaml using the Resume Builder or by copying example.gitresume.yaml
3. Connect your repo to GitResume
4. Commit and push — GitResume automatically builds your PDF and web resume

Connect to GitResume

After creating your repo from this template, follow these steps to publish it with GitResume.

Step 1: Sign in

Go to gitresume.co/login and sign in with GitHub or Google.

If you sign in with Google but your resume repo is on GitHub, that's fine — you'll connect GitHub in the next step.

Step 2: Create a project

On the dashboard, click New Project (this takes you to the setup wizard).

2a — Grant repository access (first time only)

The wizard will prompt you to grant the GitResume GitHub App access to your repos. Pick:

• Only select repositories (recommended) — choose just this resume repo
• All repositories — convenient but broader than necessary

You can adjust this later from GitHub → Settings → Applications → GitResume, or directly at https://github.com/apps/gitresume-co/installations/select_target.

2b — Select your repo

Pick the repo you just created from the template. Use the search box if you have many repos.

2c — Fill in project details

• Project name — defaults to the repo name; edit if you want
• Slug — auto-generated from the name; the field shows a live URL preview. This becomes your public URL: gitresume.co/@<your-username>/<slug>. Lowercase letters, numbers, and hyphens only.

Click Create Project.

Using a filename other than gitresume.yaml (e.g. cv.yaml)? Create the project with the default first, then update Resume Path in the project's Settings tab.

Step 3: Push your resume

Back in your local clone:

# If you haven't already, copy the example as a starting point
cp example.gitresume.yaml gitresume.yaml

# Edit gitresume.yaml, then:
git add gitresume.yaml
git commit -m "add my resume"
git push

GitResume's webhook receives the push and starts building automatically. Watch the build status on your project page; once green:

• PDF — downloadable from the project dashboard
• Web — published at gitresume.co/@<your-username>/<slug>

No webhook fired? Click Build Now on the project page to trigger one manually.

Tailoring for specific applications

Push to any non-default branch to build a tailored variant without touching your public resume:

git checkout -b company-acme
# edit gitresume.yaml to emphasise relevant experience
git commit -am "tailor for Acme"
git push -u origin company-acme

Branch builds appear in your project's build list alongside the main branch's builds, tagged with the branch name.

Editor Setup

Autocompletion and validation work out of the box: GitResume is listed in SchemaStore, so editors recognize gitresume.yaml (and *.gitresume.yaml) by filename alone. In VS Code, install the YAML extension (Red Hat); JetBrains IDEs and Neovim (with SchemaStore support) work without extra setup. See example.gitresume.yaml for reference.

Use with an AI Agent

Any AI agent that speaks MCP (Claude, Claude Code, VS Code, and others) can maintain this resume for you. The work splits in two:

• The Git side happens in this repo. The agent edits gitresume.yaml, commits, and pushes. AGENTS.md in this repo tells it how: branch first, validate against the schema, quote the public URL exactly.
• The GitResume side happens over MCP. Connect GitResume's server and the same conversation can also check whether the build passed, validate the YAML before you push, fetch the PDF link, and publish.

Claude Code:

claude mcp add --transport http gitresume https://gitresume.co/mcp

Claude (web and desktop): Settings → Connectors → Add custom connector, paste https://gitresume.co/mcp as the server URL, and leave the two OAuth fields empty. Your browser opens to approve the permissions on first use, and read-only access is a valid choice.

The MCP server never writes resume content. Every change still goes through this repo and Git, so your history stays yours. Full setup and the tool list: AI Integration.

Resources

• Getting Started — Full setup guide
• YAML Schema Reference — All available fields
• AI Integration — Connect Claude, Claude Code, or any MCP client