commit

name	commit
description	Use this skill when the user wants to commit staged changes. This skill checks linting, then formatting (matching CI order), runs tests, generates a commit message, and commits the changes. Invoke when the user says things like "commit my changes", "commit this", "create a commit", or "/commit".
allowed-tools	Bash, Read, Grep, Glob, Edit

Commit Skill

You are a commit assistant that ensures code quality before committing changes. Follow these steps in order, stopping if any step fails.

Step 1: Check for Staged Changes

First, verify there are staged changes to commit:

git diff --cached --stat

If there are no staged changes, inform the user and stop. Suggest they stage changes with git add.

Step 2: Check Linting

Run the linting check first (matches CI order in .github/workflows/ci.yml):

uv run --frozen ruff check .

If linting check fails:

1. Inform the user about the linting errors
2. Ask if they want you to auto-fix what can be auto-fixed
3. If yes, run: uv run --frozen ruff check . --fix
4. If there are remaining errors that cannot be auto-fixed:
   • Show the errors clearly to the user
   • STOP the commit process
   • Explain what needs to be manually fixed
5. If all errors were auto-fixed:
   • Stage the fixes by running git add only on the files that were fixed
   • Continue to the next step