# Commit > Create well-formatted commits following conventional commit standards. - Skill: `jeudy100/commit` (Agent Skill) - Install (CLI): `npx skillmds@latest add jeudy100/commit` - Raw SKILL.md: https://api.skillmd.com/api/skills/jeudy100/commit/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: jeudy100 (https://skillmd.com/u/jeudy100) - Updated: 2026-09-10 - Page: https://skillmd.com/skills/jeudy100/commit --- # commit Create well-formatted commits following conventional commit standards. ## Usage ``` /commit ``` Options: - `--all` or `-a` - Stage all changes before committing - `--amend` - Amend the previous commit (use with caution) - `--no-verify` - Skip pre-commit hooks - `--message ` or `-m ` - Use provided message instead of generating one ## Instructions ### Step 1: Gather Git State ```bash # Current branch git branch --show-current # Check if in detached HEAD state git symbolic-ref -q HEAD || echo "DETACHED HEAD" # Staged changes (file names and status) git diff --cached --name-status # Staged changes (actual diff content for understanding changes) git diff --cached # Unstaged changes git diff --name-status # Untracked files (not recursive to avoid huge output) git ls-files --others --exclude-standard # Recent commits for context git log --oneline -5 ``` **Important:** Read the full `git diff --cached` output to understand what changed, not just which files. This is essential for generating accurate commit messages. ### Step 2: Stage Changes If `--all` flag is used: ```bash git add -A ``` Otherwise, if there are no staged changes but there are unstaged/untracked files: ``` Question: "No changes are staged. What would you like to commit?" Options: - Stage all changes (git add -A) - Stage specific files (list files) - Cancel ``` If staging specific files, use: ```bash git add ... ``` ### Step 3: Generate Commit Message If `--message` flag is provided, use the provided message. Otherwise, analyze staged changes and generate a conventional commit message: **Conventional Commit Format:** ``` ():