Setup Git by probabl-ai — AI Skill for Any LLM

Overview

Publisher	probabl-ai
Repository	`skore-skills`
Skill name	`setup-git`
Stars	144
Forks	9
Bundled files	1
License	BSD-3-Clause
Links	Skill source Repository Homepage

Markdown instructions

A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

Works with any LLM

AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

1 bundled files

Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

Open source

Published by probabl-ai on GitHub. Read the source before you install it.

Installation

Install the Setup Git AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/probabl-ai/skore-skills/tree/main/skills/setup-git
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/probabl-ai/skore-skills.git /tmp/skore-skills
mkdir -p .claude/skills
cp -r /tmp/skore-skills/skills/setup-git .claude/skills/setup-git

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Setup Git in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Setup Git on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Setup Git is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed

The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

Switch models mid-chat

Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Set Up Git

Pre-change snapshot

Run this section only when setup-ml-project loaded this skill for the pre-change snapshot. Do not run Lookup. Do not scaffold. Do not ask whether later stages commit. Then return to setup-ml-project.

Run python -m skore_skills git snapshot.
action skip and reason already: return. Do not persist again.
action skip and reason clean or nothing_to_commit: persist python -m skore_skills policy set git.snapshot skipped, then return. Do not ask. Do not git commit.
action ask: AskUserQuestion. Recommend committing. In 2–4 lines, say this commit records the workspace as it is now, so the user can return to it before setup changes anything. It does not change whether later stages commit. A file link is an addition, never the context.
- No: persist python -m skore_skills policy set git.snapshot declined. Do not git init, git add, or git commit. Return.
- Yes: continue. Persist python -m skore_skills policy set git.snapshot committed after the commit exits 0.
On yes, if repo is false, run git init -b main before adding files. The initial branch is main. Do not git config. Do not name that branch master.
If ambiguous_dotfiles or review_paths is non-empty, ask once which of those paths to keep tracked. List every hidden path and each review path with its kind. Say that paths they do not keep are ignored. Do not ask a second question for the other list. Copy paths from the JSON. Then:
- ambiguous_dotfiles was non-empty → python -m skore_skills git ignore-merge --decide plus --keep <path> for each chosen hidden path (no --keep if they keep none).
- review_paths was non-empty → python -m skore_skills git review-decide with --keep <path> for each chosen path and --ignore <path> for every other path in that list (no --keep if they keep none). Pass a folder path through with its trailing slash.
Empty lists: do not ask, and do not run git ignore-merge. Never --keep .env or .skore. Exit code 2 from those commands is structured JSON, not a command failure.
git status. git add -- <paths> only staged paths that are not still listed in review_paths, plus hidden paths the user kept. Never stage .env, .skore, .venv, .pixi, or another must-ignore tool directory. Never stage a review path that was not kept.
git commit -m "<one-line subject>". The subject states that this is the workspace before setup changes it. Only this section uses that subject.

Lookup

Run status first. Take the first row that matches, then run its steps from the Sequence below. Do not stop after reading the table.

`policy.git.autocommit`	Situation	Steps	Ask	Commit
`on` or `off`, user asks to change it	HEAD exists, or the new value is `off`	1, 9	the autocommit question only	no
`on` or `off`, user asks to change it	new value `on`, no HEAD	1, 7, 8, 9	autocommit, then one keep question if `review_paths` is non-empty	yes
`null`	any	2, 3, 4, then only the Ask and Commit of the row for the persisted answer. Do not run steps 2 or 3 again	autocommit once	per that row
`off`	any	2, 3, 5, 9	nothing	no
`on`	`policy.git.snapshot` is `committed` and `git status` is dirty	2, 3, 7, 8, 9	one keep question only if `ambiguous_dotfiles` or `review_paths` is non-empty	yes, the setup changes only
`on`	HEAD exists	2, 3, 6, 9	nothing	no
`on`	no HEAD	2, 3, 7, 8, 9	one keep question only if `ambiguous_dotfiles` or `review_paths` is non-empty	yes

The keep question is one question. After step 3 it lists every hidden path and every review path with its kind. The change-to-on row did not run ignore-merge: list only review_paths. Exit code 2 from git ignore-merge, git review, or git review-decide is structured JSON, not a command failure.

Sequence

Run python -m skore_skills status. If the user asked to change the commit choice and policy.git.autocommit is already on or off, re-ask that question and persist on or off. Do not git init. Do not git ignore-merge. If the new value is on and the repo has no HEAD yet, continue at the first-commit review (step 7). If the new value is off, or on and HEAD exists, stop this sequence: use the return rule in step 9 and do not continue at step 2. Do not invent another commit. Later stages follow the new value. Otherwise, if autocommit is already on or off, do not ask that question again.
If there is no .git directory, run git init -b main. The initial branch is main. Do not run git config. Do not name that branch master. Do not rename a branch that already exists.
Run python -m skore_skills git ignore-merge. Keep the JSON ambiguous_dotfiles list. Exit code 2 is that structured list, not a command failure. Do not ask yet.
If policy.git.autocommit is null, ask once: should later stages persist with git commit (on) or never (off)? State in 2–4 lines what the answer authorizes — commits at the end of later stages, starting with the first commit this turn — and which paths stay ignored; a file link is an addition, never the context. Persist with python -m skore_skills policy set git.autocommit on or off. That answer is also consent for the first commit. It does not authorize tracking ambiguous_dotfiles or review_paths. When setup-ml-project already persisted on or off this turn, do not ask again.
If autocommit is off, stop. Do not ask which files to keep. Do not git commit. Use the return rule in step 9.
If autocommit is on and HEAD exists, stop after ignore-merge. Do not use this step when policy.git.snapshot is committed and git status is dirty; that row commits the setup changes. Do not ask which files to keep. Do not invent another commit. Later stages use python -m skore_skills git end-turn --stage <stage> then persist-ml-git, where <stage> is setup, data_analysis, implement, evaluate, or backlog. When that skill is not installed, those stages report the pending paths instead of committing.
If autocommit is on and (this repo has no HEAD yet, or policy.git.snapshot is committed and git status is dirty), run python -m skore_skills git review. When git.snapshot is committed, the step 8 commit is only the changes since that snapshot. Do not ask to snapshot again. When this step is reached from step 1, ignore-merge did not run: use only review_paths. If ambiguous_dotfiles and review_paths are both empty, do not ask. If either list is non-empty, ask once which of those paths to keep tracked. List every hidden path and each review path with its kind. Say that paths they do not keep are ignored. Do not ask a second question for the other list. Copy paths from the JSON; do not reclassify them. Do not ask about file size, artifacts, or datasets when review_paths is empty, and do not ask about hidden files when ambiguous_dotfiles is empty. Then:
- ambiguous_dotfiles was non-empty → re-run python -m skore_skills git ignore-merge --decide plus --keep <path> for each chosen hidden path (no --keep if they keep none).
- review_paths was non-empty → python -m skore_skills git review-decide with --keep <path> for each chosen path and --ignore <path> for every other path in that list (no --keep if they keep none). Pass a folder path through with its trailing slash so the ignore line is that folder. Exit code 2 from git review or git review-decide is the structured review outcome, not a generic command failure: read its JSON. The question in this step is that decision; do not ask again. If review-decide still lists paths, rerun it with the same choices.
Run only the command for a list that was non-empty. Do not re-ask paths gone from the next JSON. Never --keep .env or .skore.
Then git status. git add -- <paths> only paths that are not still listed in review_paths, and git commit -m "<one-line subject>" from this setup turn. The subject describes the files committed now. It does not say this commit is the state before setup changes. Do not ask a second time about autocommit. Never stage .env or .skore.
When setup-ml-project dispatched this turn and is in this session, return control to it. Otherwise load triage-ml-task if status.skills reports it installed, else stop.

Stop conditions

Never overwrite .gitignore; git ignore-merge unions packaged rules.
Never stage .env, .skore, or a review path that was not kept.
Never split hidden files and review paths into two questions before the first commit.
Never push, create a remote, amend, rebase, or set git identity.
The initial branch is main. Do not name it master. Do not rename a branch that already exists.
Do not call python -m skore_skills git end-turn --stage … to create the first commit.
The pre-change snapshot does not scaffold. It does not run git ignore-merge unless ambiguous_dotfiles was non-empty.
Lookup does not use the pre-change snapshot commit subject.

Frequently asked questions

What does the Setup Git AI skill do?

Initialize safe version control, including an optional commit of the tree before setup changes it. Trigger when the user asks to initialize version control, add ignore rules, or make the first commit. This action owns first-time git setup only. Before the first commit, ask once which unknown hidden files and review paths to keep tracked. When loaded for the pre-change snapshot, commit the current tree before other setup writes, then return.

Why use Setup Git on TypingMind?

Because you install it once and use it with any model. Setup Git is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Setup Git in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/probabl-ai/skore-skills/tree/main/skills/setup-git. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Setup Git?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Setup Git?

As many as you like. As long as a model supports skills, you can use Setup Git with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Setup Git AI skill free?

Yes. It is published on GitHub by probabl-ai under the BSD-3-Clause license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Set Up Git

Pre-change snapshot

Lookup

Sequence

Stop conditions

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now