How do I install the Git Workflow skill?

Run npx skillmds@latest add tomevault-io/git-workflow-163 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. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. 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

Git Workflow

Git workflow patterns for branching, committing, PR preparation, and conflict resolution. Use when the task involves git operations, branch management, commit messages, or PR workflows. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

When to use

Git workflow patterns for branching, committing, PR preparation, and conflict resolution.

On-demand loading: Read this skill only when the task clearly matches the description above. Do not load for unrelated work.

Git Workflow Skill

Use this skill when the task involves git operations, commit preparation, branch management, or PR workflows.

Branching Conventions

Detect the repo's branching model from git log and branch names
Common patterns: feature/, fix/, refactor/, hotfix/, release/*
Never push directly to main/master unless the repo explicitly allows it

Commit Discipline

Prefer conventional commits: type(scope): description
One logical change per commit
Imperative mood in commit messages
Body explains WHY, not WHAT (the diff shows WHAT)

PR Preparation

All CI checks must pass before requesting review
Remove debug code (console.log, debugger, TODO)
Update docs if behavior changed
Include test coverage for new code
Draft clear PR description with context

Conflict Resolution

Pull/rebase before starting new work
Resolve conflicts by understanding both sides, not by accepting one blindly
After resolving, run full test suite

Anti-patterns

Do not force push to shared branches
Do not commit .env, credentials, or build artifacts
Do not create massive PRs (prefer <400 lines changed)
Do not mix refactoring with feature work in one PR

Source: kscius/KS-Cursor-Orchestrator — distributed by TomeVault.

Frequently asked questions