# Create Git Commit Create an atomic git commit with a properly formatted commit message following best practices for the uncommited changes or these specific files if specified. Specific files (skip if not specified): - File 1: $1 - File 2: $2 - File 3: $3 - File 4: $4 - File 5: $5 ## Instructions **Commit Message Format:** - Use conventional commits: `: ` - Types: `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore` - Present tense (e.g., "add", "fix", "update", not "added", "fixed", "updated") - 50 characters or less for the subject line - Lowercase subject line - No period at the end - Be specific and descriptive **Examples:** - `feat: add web search tool with structured logging` - `fix: resolve type errors in middleware` - `test: add unit tests for config module` - `docs: update CLAUDE.md with testing guidelines` - `refactor: simplify logging configuration` - `chore: update dependencies` **Atomic Commits:** - One logical change per commit - If you've made multiple unrelated changes, consider splitting into separate commits - Commit should be self-contained and not break the build **IMPORTANT** - NEVER mention claude code, anthropic, co authored by or anything similar in the commit messages ## Run 1. Review changes: `git diff HEAD` 2. Check status: `git status` 3. Stage changes: `git add -A` 4. Create commit: `git commit -m ": "` 5. Push to remote: `git push -u origin $(git branch --show-current)` 6. Verify push: `git log origin/$(git branch --show-current) -1 --oneline` ## Report Output in this format (plain text, no markdown): Commit: Branch: Message: Pushed: Yes (or No if push failed) Files: files changed Then list the files: - - - ... **Example:** ``` Commit: a3c2f1e Branch: feat/add-user-auth Message: feat: add user authentication system Pushed: Yes Files: 5 files changed - src/auth/login.py - src/auth/middleware.py - tests/auth/test_login.py - CLAUDE.md - requirements.txt ```