# Git Workflow > Git commit message format using conventional commits, with character limits, commit types, branch workflow, and examples. Load before making a commit or reviewing git history. Use when this capability is needed. - Skill: `tomevault-io/git-workflow-69` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/git-workflow-69` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/git-workflow-69/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/git-workflow-69 --- # Git Workflow Conventions Read this skill before making a commit. It contains the full commit message format, character limits, conventional commit types, and examples. --- ## Commit Protocol (CRITICAL) - **NEVER commit automatically** - always wait for explicit confirmation Whenever asked to commit changes: - Stage the changes - Write a detailed but concise commit message using conventional commits format - 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 ():