Git Workflow

Organization

ovh

git-workflow

Manage git branches, commits, rebases, and pull requests following project conventions

Overview

Publisher	ovh
Repository	`shai`
Skill name	`git-workflow`
Stars	627
Forks	60
Bundled files	Instructions only
License	Apache-2.0
Links	Skill source Repository

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.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by ovh on GitHub. Read the source before you install it.

Installation

Install the Git Workflow 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/ovh/shai/tree/main/shai-core/examples/skills/git-workflow
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/ovh/shai.git /tmp/shai
mkdir -p .claude/skills
cp -r /tmp/shai/shai-core/examples/skills/git-workflow .claude/skills/git-workflow

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

Use it in TypingMind

Enable Git Workflow 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 Git Workflow 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 Git Workflow 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.

Git Workflow

Purpose

Handle common git operations cleanly and safely, following the project's branching and commit conventions.

Commit Conventions

Write clear, concise commit messages in the imperative mood (e.g., "Add feature X", not "Added feature X").
Prefix commits with a type tag when applicable: feat:, fix:, docs:, refactor:, test:, chore:, ci:.
Keep the subject line under 72 characters.
Add a blank line after the subject line, then a detailed body explaining what and why (not how).

Branch Naming

Use descriptive branch names: feat/<name>, fix/<name>, chore/<name>.
Use lowercase kebab-case.

Procedure

Before Committing

Run git status and git diff --staged to review what will be committed.
Ensure no debug prints or temporary files are staged.
Run cargo fmt and cargo clippy before committing.

Creating a Commit

bash
git add -p   # stage specific hunks interactively
git commit -m "feat: short description" -m "Detailed explanation of the change."

Rebasing

Always rebase onto the target branch before opening a PR:

bash
git fetch origin
git rebase origin/main

Resolve conflicts file by file, then git rebase --continue.

Opening a Pull Request

Push the branch: git push -u origin <branch-name>.
Use a descriptive PR title and description.
Link any related issues.

Safety Rules

Never force-push to main.
Never commit secrets or credentials.
Always confirm with the user before pushing or force-pushing.
Use --force-with-lease instead of --force when force-pushing.

Frequently asked questions

What does the Git Workflow AI skill do?

Manage git branches, commits, rebases, and pull requests following project conventions

Why use Git Workflow on TypingMind?

Because you install it once and use it with any model. Git Workflow 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 Git Workflow in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ovh/shai/tree/main/shai-core/examples/skills/git-workflow. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Git Workflow?

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 Git Workflow?

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

Is the Git Workflow AI skill free?

Yes. It is published on GitHub by ovh under the Apache-2.0 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.

View all

Release Openclaw Mac

openclaw

OrganizationPopular

Run or recover OpenClaw macOS release signing, notarization, appcast, and asset promotion.

Release Openclaw Maintainer

openclaw

OrganizationPopular

Prepare, publish, recover, or verify OpenClaw beta, stable, and extended-stable releases, including approved backports.

Release Openclaw Plugin Testing

openclaw

OrganizationPopular

Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E,…

Solid

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Git Workflow

Purpose

Commit Conventions

Branch Naming

Procedure

Before Committing

Creating a Commit

Rebasing

Opening a Pull Request

Safety Rules

Frequently asked questions

Related AI Skills

Set up your own AI workspace now