How do I install the Git skill?

Run npx skillmds@latest add tomevault-io/git-20 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git by tomevault-io — Agent Skill

Name: Git
Author: tomevault-io

Git

Git hygiene for multi-agent collaborative work. Use when performing version control operations, syncing with remote, committing changes, or ensuring work is properly shared with the team. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Git Skill

This skill covers git hygiene for multi-agent collaborative work.

Core Principle: Pull First, Always

This is a multi-agent team environment with rapid, concurrent changes.

Before doing ANY local work—reading files, making edits, or starting a task—you MUST sync with remote:

git pull --rebase

Why This Matters

Multiple agents (human and AI) are working on this repository simultaneously. Without pulling first:

You may be reading stale files that have already been modified
Your edits may create merge conflicts with work that's already on remote
You risk overwriting someone else's changes

When in doubt, pull. It's always safe to pull; it's never safe to assume you're current.

Sync Cadence

Event	Git Action
FIRST thing—before any action	`git pull --rebase`
Before starting any task	`git pull --rebase`
Before reading files for context	`git pull --rebase` (if not just pulled)
After each meaningful edit	`git add . && git commit -m "..."`
After completing a task	`git push`
Before ending any session	Full sync and push

Commit Message Format

<type> #<issue-id>: <short description>

Types: feat, fix, docs, refactor, chore

Examples:

docs #12: Add RaaS pricing section to whitepaper
fix #7: Correct diagram alignment in Stage A
refactor #15: Reorganize repository architecture section

Session Completion Workflow

When ending a work session, complete ALL steps:

git add .
git commit -m "chore: session checkpoint"
git pull --rebase
git push

Then verify:

git status  # MUST show "up to date with origin"

Critical Rules

Work is NOT complete until git push succeeds
NEVER stop before pushing—that leaves work stranded locally
NEVER say "ready to push when you are"—YOU must push
If push fails, resolve conflicts and retry until it succeeds

Quick Reference

git pull --rebase                       # FIRST! Get latest before ANY work
git add . && git commit -m "msg"        # Save work
git push                                # Share work
git status                              # Check state

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: git-20description: Git hygiene for multi-agent collaborative work. Use when performing version control operations, syncing with remote, committing changes, or ensuring work is properly shared with the team. Use when this capability is needed.---# Git SkillThis skill covers git hygiene for multi-agent collaborative work.## Core Principle: Pull First, Always**This is a multi-agent team environment with rapid, concurrent changes.**Before doing ANY local work—reading files, making edits, or starting a task—you MUST sync with remote:```bashgit pull --rebase```### Why This MattersMultiple agents (human and AI) are working on this repository simultaneously. Without pulling first:- You may be reading **stale files** that have already been modified- Your edits may create **merge conflicts** with work that's already on remote- You risk **overwriting someone else's changes****When in doubt, pull.** It's always safe to pull; it's never safe to assume you're current.## Sync Cadence| Event | Git Action ||-------|------------|| **FIRST thing—before any action** | `git pull --rebase` || Before starting any task | `git pull --rebase` || Before reading files for context | `git pull --rebase` (if not just pulled) || After each meaningful edit | `git add . && git commit -m "..."` || After completing a task | `git push` || Before ending any session | Full sync and push |## Commit Message Format```<type> #<issue-id>: <short description>Types: feat, fix, docs, refactor, chore```Examples:- `docs #12: Add RaaS pricing section to whitepaper`- `fix #7: Correct diagram alignment in Stage A`- `refactor #15: Reorganize repository architecture section`## Session Completion WorkflowWhen ending a work session, complete ALL steps:```bashgit add .git commit -m "chore: session checkpoint"git pull --rebasegit push```Then verify:```bashgit status # MUST show "up to date with origin"```### Critical Rules- Work is NOT complete until `git push` succeeds- NEVER stop before pushing—that leaves work stranded locally- NEVER say "ready to push when you are"—YOU must push- If push fails, resolve conflicts and retry until it succeeds## Quick Reference```bashgit pull --rebase # FIRST! Get latest before ANY workgit add . && git commit -m "msg" # Save workgit push # Share workgit status # Check state```---> Converted and distributed by [TomeVault](https://tomevault.io/claim/zacharyluz) — claim your Tome and manage your conversions.

Frequently asked questions

Git