Git Commit

Guide the user through creating a focused, well-described git commit. This skill works in any Git repository.

Commits happen frequently during development -- they protect against lost work and repository damage. Speed and clarity matter.

Workflow

Step 1: Review Changes

Show the user what has changed so they can decide what to commit.

1. Run git status to display staged and unstaged changes.
2. Run git diff (unstaged) and git diff --staged (staged) to show the content of changes.
3. If there are no changes at all (clean working tree with nothing staged), inform the user there is nothing to commit and stop.

Step 2: Stage Files

Determine which files to include in this commit.