How to get the latest version of NEO
This guide explains, step by step, how to update your local copy of the NEO-releases repository every time the technical team pushes a new feature, a change, or a fix to the main branch, main.
1. Why do I have to do this?
The NEO repository lives in GitLab, on a server shared by the whole team. When someone pushes an improvement (a new skill, a corrected playbook, a configuration tweak), that improvement is stored there, in GitLab — it doesn't reach your computer on its own.
Think of it as a shared folder in the cloud: if a teammate adds a new file, it doesn't automatically show up in your local copy until you "sync" it. In Git, that sync is called doing a pull ("pulling" the changes).
In short: if you don't repeat this process every now and then, you'll keep working with an old version of the skills and playbooks, without the improvements or fixes that are already available.
2. When do I have to do this?
Do this process every time:
| Situation | Example |
|---|---|
| The technical team lets you know they pushed an improvement or a fix | "The issue with the regression playbook is fixed, update your copy" |
| You're about to start working after a few days without touching the project | You start your day and want to make sure everything is up to date before using the assistant |
| You notice that a skill or a playbook doesn't behave the way a new guide explained | Your local copy may not have that change yet |
IMPORTANT! This process assumes you already have the NEO-releases repository downloaded (cloned) on your computer, inside VSCode. If this is your first time and you don't have it yet, see point 6 before continuing.
3. Before you start: what you need to have at hand
You don't need to know how to code, but you do need this:
| Item | Details |
|---|---|
VSCode open with the NEO-releases project folder |
It's the editor used together with your AI assistant (Claude Code, Codex, or Copilot) |
| Connection to the company network/VPN, if access to GitLab requires it | Without this, you won't be able to connect to the repository |
4. Step by step (with VSCode, without using the terminal)
This is the recommended way if you don't feel comfortable using commands.
Step 1 — Open the "Source Control" panel
In the left margin of VSCode, click the icon that looks like a branch with little dots (Source Control).
Step 2 — Confirm that you're on the main branch
In VSCode's integrated terminal (Ctrl + ` or Ctrl + j), inside the project folder, type:
git branch
The branch you're on has an asterisk (*) next to its name.
- If you're already on
main, continue to Step 3. - If you're on another branch, type
git checkout mainto switch.
Alternative (without the terminal): look at the bar in the bottom-left corner of VSCode — the name of the branch you're on also appears there. If it says something else, click there and choose
mainfrom the list.
Step 3 — Pull the changes ("Pull")
Still in the blue bottom bar, you'll see an icon with two circular arrows (🔄) next to the branch name. Click that icon.
Alternative: in the "Source Control" panel (Step 1), click the three dots (
...) at the top and choose Pull.
VSCode will connect to GitLab, check whether there's anything new, and if there is, it will download and apply it on its own, without you having to do anything else.
Step 4 — Confirm that it was updated
A short notification usually appears in the bottom right confirming the download. You can also confirm it by checking the history: right-click any project file in the VSCode explorer and choose "View Timeline", or open the recent commits tab in GitLab (see point 8) and compare the date of the latest commit.
5. Alternative: using the terminal (for those who feel comfortable)
If you prefer to use VSCode's integrated terminal (Ctrl + ` or Ctrl + j or the Terminal > New Terminal menu), the same four steps above come down to two commands, run inside the project folder:
git checkout main
git pull
The first command makes sure you're on the main branch; the second one pulls and applies the new changes.
6. If you don't have the repository on your computer yet
If this is the first time you're going to work with NEO-releases and you haven't downloaded it yet, do this just once:
- Open VSCode.
- Press
Ctrl + Shift + Pto open the command palette, type "Git: Clone", and choose it. -
Paste this address when it asks for it:
https://gitlab.crowdaronline.com/lippia/products/neo/neo-releases.git -
Choose the folder on your computer where you want to save it.
- When it's done, VSCode will ask whether you want to open that folder — choose "Open".
From then on, you can follow point 4 of this guide every time you want to pull the latest updates.
7. Common problems (and what to do)
| What you see | Why it may happen | What to do |
|---|---|---|
| VSCode warns that you have "local changes" or "uncommitted changes" and won't let you Pull | You modified a project file and haven't saved it (committed it) yet | Save those changes first (make a commit) or discard them if you don't need them, before repeating Step 3. If you're not sure what to do, check with the technical team before discarding anything |
| A "conflict" (merge conflict) message appears | A file was modified both in your local copy and in GitLab, on the same lines | This requires manual review — let the technical team know, don't resolve it blindly |
| The Pull throws a connection or permissions error | You don't have the VPN on, or your user doesn't have access to the repository | Check your network/VPN connection, and if the error persists, ask the technical team for access |
After updating, the assistant still shows a skill that no longer exists (for example lippia-neo-report-bug-jira) or warns that it can't load it |
The skill was removed or merged with another one in NEO-releases, but the link you created in .claude/skills/ of the test repository is still there, pointing to a folder that no longer exists |
In the folder of the test repository, delete the broken links with find .claude/skills -xtype l -delete (in Git Bash) and run the NEO-releases script that creates the links again: bash <path-to-neo-releases>/symlink-skills-bash.sh on Linux or Mac, or bash <path-to-neo-releases>/symlink-skills-win-git-bash.sh on Windows (from Git Bash as administrator). Then reload VSCode |
| You don't see any branch icon in the bottom bar | The folder open in VSCode isn't a Git repository (or isn't the right folder) | Make sure you opened the cloned NEO-releases folder, not a subfolder or a loose copy |
8. See the changes directly in GitLab (without downloading anything)
If you only want to see what changed, without downloading it to your computer yet, you can check the history directly in the browser, at:
https://gitlab.crowdaronline.com/lippia/products/neo/neo-releases/-/commits/main
There you'll see the list of changes pushed to main, with the date, author, and a short description of each one.
9. Visual summary of the flow
Someone lets you know there are updates in NEO-releases
│
▼
Open VSCode → Source Control panel
│
▼
Confirm that you're on the "main" branch
│
▼
Click the Pull icon (🔄)
│
▼
Local copy updated with the latest skills and playbooks
10. Repository in GitLab
The NEO-releases repository is located at:
https://gitlab.crowdaronline.com/lippia/products/neo/neo-releases
There you can see the code, the documentation, the commit history, and clone it if you don't have it yet (see point 6).