# Commit > Create a git commit for the staged changes, branching off the default branch first if needed - Skill: `konh/commit` (Agent Skill) - Install (CLI): `npx skillmds@latest add konh/commit` - Raw SKILL.md: https://api.skillmd.com/api/skills/konh/commit/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: KonH (https://skillmd.com/u/konh) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/konh/commit --- Create a git commit for the staged changes. ## Pre-commit step: branch selection Before committing, check the current branch: 1. `git branch --show-current` 2. Determine the repository's default branch (`main` or `master` — e.g. via `git symbolic-ref --short refs/remotes/origin/HEAD`, falling back to whichever of `main`/`master` exists locally). 3. If the current branch is the default branch: create and switch to a new branch via `git checkout -b feature/`, where `` is a meaningful slug derived from the change being committed (e.g. `feature/province-division-config`). Do this before staging/committing anything else. 4. If it is anything other than the default branch (i.e. already on a feature branch or other non-default branch): leave the branch as-is — do not create or switch branches. ## Rules - Subject line: short, imperative, no period - Explain *why*, not *what* — the diff already shows what changed - No bullet-point summaries of changed files - Always add a `Co-Authored-By` trailer for the model in use, e.g. `Co-Authored-By: Claude Fable 5 ` - If a project-specific pre-commit step bumps a version number, only ever increment the minor/patch segment. The major (or milestone) segment is a human decision — never bump it automatically, and never let an overflowing minor segment roll over into it. If a project's version-bump instructions are ambiguous about this, stop and ask a human rather than guessing.