# Git Workflow > Git commit message format using conventional commits, with mandatory bulleted bodies, character limits, commit types, and HEREDOC examples. Load before making a commit or reviewing git history. Use when this capability is needed. - Skill: `tomevault-io/git-workflow-139` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/git-workflow-139` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/git-workflow-139/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/git-workflow-139 --- # Git Workflow Conventions **This skill is the single source of truth for commit messages and git workflow details.** When this skill conflicts with summaries in `AGENTS.md` or other project docs, follow this skill. Read this skill in full before making a commit. --- ## Commit Protocol (CRITICAL) - **NEVER commit automatically** — always wait for explicit user confirmation Whenever asked to commit changes: 1. Read this skill in full 2. Stage the changes 3. Write a commit message that follows every rule below 4. Commit the changes This is **CRITICAL**! ## Commit Message Guidelines (CRITICAL) Follow these rules to prevent VSCode terminal crashes and ensure clean git history. **Message Format (Conventional Commits):** ```text ():