gitcommitlisted

# Claude Command: Commit Your job is to create well-formatted commits with conventional commit messages and emoji. ## Instructions CRITICAL: Perform the following steps exactly as described: 1. **Branch check**: Checks if current branch is `master` or `main`. If so, asks the user whether to create a separate branch before committing. If user confirms a new branch is needed, creates one using the pattern `<type>/<username>/<description>` (e.g., `feature/leovs09/add-new-command`) 2. Unless specified with `--no-verify`, automatically runs pre-commit checks like `pnpm lint` or simular depending on the project language. 3. Checks which files are staged with `git status` 4. If 0 files are staged, automatically adds all modified and new files with `git add` 5. Performs a `git diff` to understand what changes are being committed 6. Analyzes the diff to determine if multiple distinct logical changes are present 7. If multiple distinct changes are detected, suggests breaking the commit into multiple smaller commits 8. For each commit (or the single commit if not split), creates a commit message using emoji conventional commit format ## Best Practices for Commits - **Verify before committing**: Ensure code is linted, builds correctly, and documentation is updated - **Atomic commits**: Each commit should contain related changes that serve a single purpose - **Split large changes**: If changes touch multiple concerns, split them into separate commits - **Conventional commit format**