New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Teamserver Git

by mendixlabs in mendixlabs/mxcli

Commit, branch and push a Mendix project in git the way Studio Pro and Mendix Team Server expect — branches created on the server (not with git checkout -b), the mxmetadata commit note written with…

Apache-2.0Auto-check passedDevelopment

Install Teamserver Git

skills CLI
$ npx skills add mendixlabs/mxcli --skill teamserver-git -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mendixlabs/mxcli teamserver-git --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/mendix/teamserver-git .claude/skills/teamserver-git && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
teamserver-git
GitHub stars
129
Token cost
~1.5k tokens
SKILL.md length
760 words
Files
1
Skills in repo
72
Repo updated
First seen
Licence
Apache-2.0

At a glance

Commit, branch and push a Mendix project in git the way Studio Pro and Mendix Team Server expect — branches created on the server (not with git checkout -b), the mxmetadata commit note written with…

  • Tasks that involve Git workflow
  • SKILL.md covers The rule: let Studio Pro do…, Branches: create them on the…, Commit from the agent and Push the branch and the notes…, plus 3 more sections
  • Calls git
  • Tasks that involve Commit messages

What it does

Teamserver Git is an agent skill from mendixlabs/mxcli. Commit, branch and push a Mendix project in git the way Studio Pro and Mendix Team Server expect — branches created on the server (not with git checkout -b), the mxmetadata commit note written with mxcli git note, and the notes ref pushed with the branch. Use before any git commit, branch, merge, rebase or push in a Mendix app repository, and when Studio Pro shows conflicts or changes that git does not, fails to open the project, or cannot deploy a revision.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git workflow and Commit messages. It works with Git. The repository describes itself as: Mendix cli tool, a headless way to work with Mendix projects. Enables Mendix projects for use with 3rd party agentic coding tools like Claude Code and Copilot. Includes a… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Git workflow
  • Tasks that involve Commit messages

Example prompts

  • “/teamserver-git”

Requirements

  • Docker

What it can do on your machine

Read from SKILL.md and the folder at commit 5c321d0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Teamserver Git loads about 1.5k tokens when it runs. Until then it costs about 120 tokens; SKILL.md has 760 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~120
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mendixlabs/mxcli at commit 5c321d0, republished under its Apache-2.0 licence (© mendixlabs). 760 words, ~1,490 tokens.

Download SKILL.mdSave it as .claude/skills/teamserver-git/SKILL.md (or your agent's skills folder).
name
teamserver-git
description
Commit, branch and push a Mendix project in git the way Studio Pro and Mendix Team Server expect — branches created on the server (not with git checkout -b), the mx_metadata commit note written with `mxcli git note`, and the notes ref pushed with the branch. Use before any git commit, branch, merge, rebase or push in a Mendix app repository, and when Studio Pro shows conflicts or changes that git does not, fails to open the project, or cannot deploy a revision.

Working with Git on a Mendix Team Server Project

A Mendix project in git is more than its files. Studio Pro keeps four things in step that plain git does not, and a commit that skips them makes Studio Pro report conflicts nobody can see, crash on open, or refuse to deploy a revision.

WhatWhereWhat breaks without it
Model unitsmprcontents/**/*.mxunit— (git handles these)
Unit indexthe .mpr Unit table, ContentsHash per unitStudio Pro's change detection; it shows changes the files do not have
Commit metadataa git note per commit under refs/notes/mx_metadataversion check and package build for that revision; the history shows (unknown)
Brancheson the Team ServerStudio Pro 11.13 crashes opening a branch that has no upstream

The rule: let Studio Pro do version control when it can

If the user has the project open in Studio Pro, the cheapest correct commit is theirs: Version Control › Commit in Studio Pro commits, writes the note, and pushes, all in one go, even when every change in it was made with mxcli. Suggest that first. Everything below is for committing from the agent.

Branches: create them on the server

  • Never git checkout -b a branch the user will open in Studio Pro. A local-only branch has no upstream, and Studio Pro 11.13 fails to open it with "Unable to find 'system' property in 'system'".
  • Ask the user to create the branch in Studio Pro: Version Control › Manage Branch Lines… › New. That creates it on the Team Server. Then git fetch && git switch <branch>, and git tracks it as origin/<branch>.
  • If they want the agent to do it instead, it must be pushed with an upstream straight away. That is an outward action, so ask first: git switch -c <branch> && git push -u origin <branch>.
  • mxcli docker check, mxcli run --local and mxcli diag -p app.mpr warn when the checked-out branch has no upstream.

Commit from the agent

bash
mxcli fix hashes -p app.mpr                     # unit index matches the files (exit 0)
git add App.mpr mprcontents <other source you changed>
git commit -m "<what changed for the user>"
mxcli git note -p app.mpr --write               # attach the mx_metadata note
  • Stage App.mpr, mprcontents/ and the source you changed (theme/, javasource/, javascriptsource/, widgets/, mdlsource/). Never stage project-settings.user.json, *.mpr.lock, *.mpr.bak, .mendix-cache/, deployment/, theme-cache/ or .mxcli/; Mendix's .gitignore already excludes most of them.
  • mxcli fix hashes matters after anything other than mxcli or Studio Pro touched a unit file: git checkout -- mprcontents/…, git restore, a merge tool. mx check does not notice a stale index. --repair fixes it.
  • mxcli git note with no commit argument annotates every commit not pushed yet (@{upstream}..HEAD). It computes the change list from the commit itself, so run it after committing. It never overwrites a note Studio Pro wrote (--force does) and it does replace Studio Pro's placeholders. Without --write it only previews.
Show full SKILL.md (323 more words)Show less

Push the branch and the notes together, and soon

bash
git push origin <branch> refs/notes/mx_metadata
  • git push alone does not push notes.
  • While the project is open, Studio Pro fetches every few minutes, and its fetch force-replaces the local refs/notes/mx_metadata with the Team Server's copy. Any note not pushed yet is gone, and Studio Pro back-fills an "(unknown)" placeholder for the commit. If that happened, run mxcli git note -p app.mpr --write again; it replaces placeholders. Then push.
  • Pushing goes to the user's Team Server and needs their credentials (a PAT). Only push when the user asks.

Never rewrite or merge model history with git

  • No git merge, rebase or cherry-pick of model changes. The .mpr is a SQLite file; git cannot merge it, and a textual merge of mprcontents/ leaves an index that does not match the files. Studio Pro has a model-aware merge: Version Control › Merge Changes Here (Merge feature branch or Cherry Pick). Studio Pro's history on Team Server is linear for that reason.
  • No --amend or force-push of a pushed commit. Before pushing, an amend is fine: the notes.rewriteRef Studio Pro puts in .git/config carries the note. Re-run mxcli git note --write anyway; it is cheap.
  • Do not switch branches or write the model while <App>.mpr.lock exists, which means Studio Pro has the project open. mxcli refuses to write then.

Reading what Studio Pro recorded

bash
git log --notes=mx_metadata --format='%h %s%n%N' -10

A note lists ModelChanges (Added | Modified | Deleted | Moved, with unit type, name and module), the ModelerVersion, and the BranchName ("" on main). A note with "HasModelerVersion":false is a placeholder Studio Pro wrote for a commit made outside it.

Checklist

  • Suggested committing from Studio Pro when it is open
  • On a branch that exists on the Team Server (has an upstream)
  • mxcli fix hashes -p app.mpr clean
  • Only project files staged
  • mxcli git note -p app.mpr --write after the last commit
  • Pushed <branch> and refs/notes/mx_metadata together, when the user asked to push
  • No git merge, rebase, cherry-pick or force-push of model history

© mendixlabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/mendix/teamserver-git of mendixlabs/mxcli.

Open the folder on GitHubat commit 5c321d0

Compare with similar skills

Teamserver Git next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Teamserver Git compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Teamserver Git this skillmendixlabs/mxcli129—~1.5kAutomated safety check: PassApache-2.0
ToolJet Multi-Repo CommitToolJet/ToolJet41k—~1.3kAutomated safety check: PassAGPL-3.0
Git Workflow and Versioningaddyosmani/agent-skills103k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Saleor Commit Workflowsaleor/saleor23k—~575Automated safety check: PassBSD-3-Clause
Emoji Commit ConventionsbaptisteArno/typebot.io11k—~424Automated safety check: PassCustom licence

Similar skills

  • ToolJet Multi-Repo Commit

    ToolJet/ToolJet

    Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.

    41k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    103k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Saleor Commit Workflow

    saleor/saleor

    Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.

    23k GitHub stars~575 tokensUpdated today
    DevelopmentAuto-check passed

  • Emoji Commit Conventions

    baptisteArno/typebot.io

    Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.

    11k GitHub stars~424 tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Draft Pull Request Creator

    wordpress-mobile/WordPress-Android

    Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.

    3.2k GitHub stars~881 tokensUpdated today
    DevelopmentAuto-check: notes

More from mendixlabs/mxcli

All 72 skills in this repo

  • Mendix Odata Pushdown

    mendixlabs/mxcli

    Push OData query options into the SQL of a Mendix resource served by a read microflow, so $filter, $orderby, $top, $skip, $count and the key lookup reach the database instead of being silently…

    129 GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Mendix Vega Charts

    mendixlabs/mxcli

    Chart a Mendix app with Vega-Lite through a pluggable widget that takes the specification and the data as separate properties, so the model emits rows and never assembles a chart payload.

    129 GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Mendix Bulk Oql Dml

    mendixlabs/mxcli

    Run set-based INSERT, UPDATE and DELETE against Mendix entities through OQL statements, which the runtime supports and Studio Pro cannot author.

    129 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Agents

    mendixlabs/mxcli

    Author Mendix AI agent documents in MDL — Model, Knowledge Base, Consumed MCP Service and Agent, with variables, tools and multi-line prompts.

    129 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Analyze Runtime

    mendixlabs/mxcli

    Find out what a running Mendix app actually does — logs, Prometheus metrics, OpenTelemetry traces and the model catalog, joined across sources.

    129 GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • Assess Migration

    mendixlabs/mxcli

    Investigate an existing non-Mendix application (Java, .NET, Python, Node, PHP, …) and produce a structured migration assessment for Mendix.

    129 GitHub stars~3.6k tokensUpdated today
    Auto-check: notes

Works with

Categories

Questions about Teamserver Git

What does Teamserver Git do?

Commit, branch and push a Mendix project in git the way Studio Pro and Mendix Team Server expect — branches created on the server (not with git checkout -b), the mxmetadata commit note written with…. Teamserver Git is an agent skill from mendixlabs/mxcli. Commit, branch and push a Mendix project in git the way Studio Pro and Mendix Team Server expect — branches created on the server (not with git checkout -b), the mxmetadata commit note written with mxcli git note, and the notes ref pushed with the branch.

When should I use Teamserver Git?

Teamserver Git fits situations like: tasks that involve Git workflow; tasks that involve Commit messages.

How do I install Teamserver Git in Claude Code?

Run `npx skills add mendixlabs/mxcli --skill teamserver-git -a claude-code`. Or copy the skill folder (.claude/skills/mendix/teamserver-git in mendixlabs/mxcli) into .claude/skills/teamserver-git in your project. Claude Code loads it when a task matches its description.

How do I install Teamserver Git in Codex?

Run `npx skills add mendixlabs/mxcli --skill teamserver-git -a codex`. Or copy the skill folder (.claude/skills/mendix/teamserver-git in mendixlabs/mxcli) into .agents/skills/teamserver-git in your project. Codex loads it when a task matches its description.

Can I use Teamserver Git in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mendixlabs/mxcli --skill teamserver-git -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/teamserver-git, .gemini/skills/teamserver-git, .github/skills/teamserver-git and .opencode/skills/teamserver-git in your project.

What does Teamserver Git need to run?

Going by SKILL.md and its folder, Teamserver Git needs the command-line tools its instructions call (git). Our summary lists: Docker.

Does Teamserver Git access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Teamserver Git safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Teamserver Git use?

Teamserver Git is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Teamserver Git use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Teamserver Git?

Skills that share tags, products or a category with Teamserver Git: ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars) and Saleor Commit Workflow (saleor/saleor, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Teamserver Git?

mendixlabs (a GitHub organization) maintains it in mendixlabs/mxcli, which has 129 GitHub stars. The repository holds 72 skills in this directory. The repository was last updated on October 8, 2026.

Source: mendixlabs/mxcli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.