How do I install the Git Workflow skill?

Run npx skillmds@latest add tomevault-io/git-workflow-212 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.

Is Git Workflow safe to use?

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

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.

Is Git Workflow free to use?

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

Who published Git Workflow?

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

Git Workflow by tomevault-io — Agent Skill

Name: Git Workflow
Author: tomevault-io

File contents

Git Workflow & Safety Protocols

1. Safety & Confirmation

1.1 Dangerous Operations

Explicit user confirmation is REQUIRED for:

git commit (unless user pre-authorized)
git push
git reset --hard
git clean -fd
git checkout (if current branch has changes)

1.2 Command Standards

Atomic Commits: One logical change per commit.
No Parallel Git: Git relies on the index lock. Never run multiple git commands in parallel.
Rollback Protocol: checkout rollbacks require confirmation.

2. Conventional Commits Specification

Format: <type>(<scope>): <subject>

Supported Input Parameters (Mental Model):

Action: enum [commit, push, branch, log, status]
Commit Type: enum [feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert]
Commit Scope: string (optional, e.g., auth, api, ui)
Commit Message: string (max 50 chars)

Type	Description
`feat`	A new feature
`fix`	A bug fix
`docs`	Documentation only changes
`style`	Changes that do not affect the meaning of the code (white-space, formatting, etc)
`refactor`	A code change that neither fixes a bug nor adds a feature
`perf`	A code change that improves performance
`test`	Adding missing tests or correcting existing tests
`build`	Changes that affect the build system or external dependencies
`ci`	Changes to our CI configuration files and scripts
`chore`	Other changes that don't modify src or test files
`revert`	Reverts a previous commit

3. Branching Strategy

Feature Branches: feat/short-description
Bugfix Branches: fix/issue-id-description
Chore Branches: chore/description

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

---name: git-workflow-212description: Use this skill for all version control tasks, including committing, branching, pushing, and reviewing history.---# Git Workflow & Safety Protocols## 1. Safety & Confirmation### 1.1 Dangerous Operations**Explicit user confirmation is REQUIRED for:*** `git commit` (unless user pre-authorized)* `git push`* `git reset --hard`* `git clean -fd`* `git checkout` (if current branch has changes)### 1.2 Command Standards* **Atomic Commits**: One logical change per commit.* **No Parallel Git**: Git relies on the index lock. Never run multiple git commands in parallel.* **Rollback Protocol**: `checkout` rollbacks require confirmation.---## 2. Conventional Commits Specification**Format**: `<type>(<scope>): <subject>`**Supported Input Parameters (Mental Model):*** **Action**: enum [commit, push, branch, log, status]* **Commit Type**: enum [feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert]* **Commit Scope**: string (optional, e.g., auth, api, ui)* **Commit Message**: string (max 50 chars)| Type | Description || :--- | :--- || `feat` | A new feature || `fix` | A bug fix || `docs` | Documentation only changes || `style` | Changes that do not affect the meaning of the code (white-space, formatting, etc) || `refactor` | A code change that neither fixes a bug nor adds a feature || `perf` | A code change that improves performance || `test` | Adding missing tests or correcting existing tests || `build` | Changes that affect the build system or external dependencies || `ci` | Changes to our CI configuration files and scripts || `chore` | Other changes that don't modify src or test files || `revert` | Reverts a previous commit |---## 3. Branching Strategy* **Feature Branches**: `feat/short-description`* **Bugfix Branches**: `fix/issue-id-description`* **Chore Branches**: `chore/description`---> Converted and distributed by [TomeVault](https://tomevault.io/claim/till-crazy-tears-us-apart) — claim your Tome and manage your conversions.

Frequently asked questions

Git Workflow