git:20260627.5fdcb5b to git:20260827.f2233af

7 added, 46 removed. Audit A to A.

---

name: commit

description: Create a single git commit from current staged and unstaged changes with an appropriate message. Use when the user asks to commit current work.

allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*), Bash(git diff:*), Bash(git branch:*), Bash(git log:*)

---

- # Commit Skill

- Stage and commit current changes with a concise, well-formed commit message based on the diff and recent commit history.

- ## When to Use

- - After completing a change and wanting to commit it.

- - When all modifications are ready to be captured in a single commit.

- ## Agent Compatibility

- This skill is tool-agnostic and can be executed by Claude Code, Codex CLI, or Cursor CLI.

- ## Inputs

- - Current repository with uncommitted changes (staged or unstaged).

- If there are no changes to commit, report that and stop.

- Do not stage or commit unrelated user changes unless the user explicitly asked to include them.

- ## Workflow

- 1. **Gather context** by running these commands in parallel:

- ```bash

- git status

- git diff HEAD

- git branch --show-current

- git log --oneline -10

- ```

- 2. **Analyze changes** from the diff output to understand what was modified and why. If the diff contains unrelated changes, include only the files that belong to the requested work.

- 3. **Stage relevant files** using `git add` for the appropriate files. Prefer explicit paths over `git add .` when the worktree contains unrelated changes.

- 4. **Create a commit** with a concise, descriptive message that:

- - Follows the repository's existing commit message style (based on recent commits).

- - Summarizes the nature of the change (new feature, bug fix, refactor, etc.).

- - Uses imperative mood and sentence case.

- Stage and commit should be executed as efficiently as possible once the relevant scope is clear.

+ # Commit

- Do not perform extra cleanup, formatting, tests, branch changes, pushes, or PR creation unless requested separately.

+ Create one commit for the current work.

- ## Outputs

+ - Inspect `git status`, `git diff HEAD`, the current branch, and recent commits.

+ - If there is nothing to commit, report that and stop.

+ - Stage only changes relevant to the requested work; preserve unrelated user changes.

+ - Follow the repository's recent commit style and use a concise message describing the change.

- - A new git commit on the current branch.

- - Console output confirming the commit was created.

+ Do not run unrelated cleanup or tests, change branches, push, or create a PR unless requested separately.