# Commit

> Create a git commit with conventional commit format. Injects current git state automatically.

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

---


## Context

- Status: !`git status -sb`
- Diff: !`git diff HEAD --stat`
- Branch: !`git branch --show-current`
- Recent commits: !`git log --oneline -10`

## Rules

Commits are terse one-liner conventional commits: `type(scope): description`.

- type: `feat`, `fix`, `refactor`, `docs`, `test`, `chore`
- scope: affected area (module, package, or feature)
- description: imperative mood, lowercase, no period, under 72 characters
- Never use "and" in a commit message. Two changes = two commits.

Stage files by name (never `git add -A` or `git add .`). Group changes by intent.

## Task

Based on the context above, stage the relevant files and create the commit.
Do not use any other tools. Do not send any text besides the tool calls.