# Commit > Create a well-formatted git commit following best practices Use when this capability is needed. - Skill: `tomevault-io/commit-10` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/commit-10` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/commit-10/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/commit-10 --- # Git Commit Workflow Follow these steps to create a high-quality commit: ## 1. Review Changes - Use `git_status` to see what files have changed - Use `git_diff` to review the actual changes - Ensure you understand what's being committed ## 2. Write Commit Message Create a commit message that: - Starts with a concise summary (50 chars or less) - Uses imperative mood ("Add feature" not "Added feature") - Includes details in the body if needed - References any relevant issue numbers ## 3. Stage and Commit - Stage only the relevant files (avoid staging unrelated changes) - Use `run_shell` to execute: `git add ` - Use `run_shell` to execute: `git commit -m "Your message"` ## 4. Verify - Use `git_log` to confirm the commit was created correctly - Use `git_diff` with staged flag to ensure nothing unexpected was committed ## Format Example ``` Add user authentication feature - Implement JWT token generation - Add login/logout endpoints - Update user model with password hashing Fixes #123 ``` --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/amaiya) — claim your Tome and manage your conversions.