Smart Commit

Simple, validated commit creation. Run checks locally, no agents needed for standard commits.

Quick Start

/commit

Workflow

Phase 1: Pre-Commit Safety Check

# CRITICAL: Verify we're not on dev/main
BRANCH=$(git branch --show-current)
if [[ "$BRANCH" == "dev" || "$BRANCH" == "main" || "$BRANCH" == "master" ]]; then
  echo "STOP! Cannot commit directly to $BRANCH"
  echo "Create a feature branch: git checkout -b issue/<number>-<description>"
  exit 1
fi

Phase 2: Run Validation Locally

Run every check that CI runs:

# Backend (Python)
poetry run ruff format --check app/
poetry run ruff check app/
poetry run mypy app/

# Frontend (Node.js)
npm run format:check
npm run lint
npm run typecheck

Fix any failures before proceeding.

Phase 3: Review Changes

git status
git diff --staged   # What will be committed
git diff            # Unstaged changes

Phase 4: Stage and Commit

# Stage files
git add <files>
# Or all: git add .

# Commit with conventional format
git commit -m "<type>(#<issue>): <brief description>

- [Change 1]
- [Change 2]

Co-Authored-By: Claude <noreply@anthropic.com>"

# Verify
git log -1 --stat

Commit Types

Rules

1. Run validation locally – Don’t spawn agents to run lint/test
2. NO file creation – Don’t create MD files or documentation
3. One logical change per commit – Keep commits focused
4. Reference issues – Use #123 format in commit message
5. Subject line < 72 chars – Keep it concise

Quick Commit

For trivial changes (typos, single-line fixes):

git add . && git commit -m "fix(#123): Fix typo in error message

Co-Authored-By: Claude <noreply@anthropic.com>"

Related Skills

• create-pr: Create pull requests from commits
• review-pr: Review changes before committing
• fix-issue: Fix issues and commit the fixes
• issue-progress-tracking: Auto-updates GitHub issues with commit progress

References

• Conventional Commits
• Recovery