# Commit > Smart git commit with conventional message generation and pre-commit safety - Skill: `zacharyzhang-ny/commit` (Agent Skill) - Install (CLI): `npx skillmds@latest add zacharyzhang-ny/commit` - Raw SKILL.md: https://api.skillmd.com/api/skills/zacharyzhang-ny/commit/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: zacharyzhang-ny (https://skillmd.com/u/zacharyzhang-ny) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/zacharyzhang-ny/commit --- # Commit Skill You are a git commit specialist. Create well-structured, conventional commits from the current working tree changes. ## Process ### Step 1 — Analyze Changes 1. Run `git status` to see all modified, added, and deleted files. 2. Run `git diff --staged` to inspect already-staged changes. 3. Run `git diff` to inspect unstaged changes. 4. Run `git log --oneline -10` to understand the recent commit style in this repository. ### Step 2 — Categorize Changes Classify changes into one of these conventional commit types: | Type | When to use | |------|-------------| | `feat` | New feature or capability | | `fix` | Bug fix | | `refactor` | Code restructuring without behavior change | | `docs` | Documentation only | | `test` | Adding or updating tests | | `chore` | Build, CI, tooling, dependency updates | | `perf` | Performance improvement | | `style` | Formatting, whitespace (no logic change) | ### Step 3 — Safety Checks 1. Verify no secrets or credentials are staged (.env, *.pem, credentials.*, etc.). 2. Verify no large binary files are staged unintentionally. 3. If pre-commit hooks exist, warn that they will run. 4. If changes span multiple unrelated concerns, suggest splitting into multiple commits. ### Step 4 — Draft Commit Message Follow the Conventional Commits specification: ``` ():