Name: Commit
Author: baptisteArno

Commit Current Changes

Use this skill when the user asks to commit the current worktree changes.

Workflow

Inspect the worktree before committing:
- git status --short
- git diff --staged
- git diff
- git log --oneline -5
Review all staged and unstaged changes that will be part of the commit.
Stage the relevant files, but never include likely secrets such as .env files or credential dumps.
Write a concise commit message in the repository's usual style.
Prefix the message with the single emoji that best matches the dominant change.
Create the commit and confirm success with git status --short.

If there is nothing to commit, say so instead of creating an empty commit.

Use this skill when the user asks to commit the current worktree changes.

Inspect the worktree before committing:
- git status --short
- git diff --staged
- git diff
- git log --oneline -5
Review all staged and unstaged changes that will be part of the commit.
Stage the relevant files, but never include likely secrets such as .env files or credential dumps.
Write a concise commit message in the repository's usual style.
Prefix the message with the single emoji that best matches the dominant change.
Create the commit and confirm success with git status --short.

If there is nothing to commit, say so instead of creating an empty commit.