# Commit

> Stage the current changes and create a git commit with a conventional commit message. Use when committing, saving, or recording changes to git — e.g. "commit my changes", "stage and commit", "create a commit". Do NOT use for only drafting a commit message without committing (that is the commit-message command), or for pushing or amending commits.

- Skill: `christiangalsterer/commit` (Agent Skill)
- Install (CLI): `npx skillmds@latest add christiangalsterer/commit`
- Raw SKILL.md: https://api.skillmd.com/api/skills/christiangalsterer/commit/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: christiangalsterer (https://skillmd.com/u/christiangalsterer)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/christiangalsterer/commit

---


# Commit

Stage the current changes and create a git commit. All commit message
formatting rules (types, scopes, subject/body conventions) are defined in
the `commit-message` command — do NOT duplicate them here. This skill only
adds staging and committing on top.

## Steps

1. Run `git status --short` to see the current changes.
2. Stage the changes with `git add` — stage everything by default; if the
   user asked to commit only specific files, stage just those.
3. Run the `/commit-message` command to draft the commit message. Follow
   its output exactly — it defines the format, types, scopes, and style
   rules.
4. Show the drafted message to the user and ask for confirmation.
5. On confirmation, create the commit with `git commit -m "<message>"`.
   Quote the message safely and do not append any Co-Authored-By line.

## Rules

- Do NOT push the commit unless the user explicitly asks.
- Do NOT amend existing commits.
- Do NOT invent commit message rules — defer to the `commit-message` command.