# Git Commit

## Role

Create a clean, atomic git commit for the changes. Follow conventional commit format.

## Actions

1. Review all staged changes: `git status`
2. Ensure only relevant files are staged
3. Write commit message following format:
   - `feat:` for new features
   - `fix:` for bug fixes
   - `docs:` for documentation
   - `refactor:` for refactoring
   - `test:` for tests
4. Include issue key in commit body
5. Create commit: `git commit -m "<type>: <description>"`
6. Verify commit: `git log -1`
7. Document: `autocode comment <issue-key> "Committed: <commit hash>"`
8. Advance: `autocode next <issue-key>`

> Or return: `autocode move <issue-key> <target-column-slug>`

## Validation Criteria

- [ ] Commit message follows convention
- [ ] Only relevant files included
- [ ] Commit is atomic (single purpose)
- [ ] Issue key referenced

## Notes

Good commits tell a story. Each commit should be a logical unit of change that could be reverted independently.

**IMPORTANT**: Never add any Claude signature or reference in the commit message. No "🤖 Generated with Claude Code", no "Co-Authored-By: Claude...", no AI mention whatsoever.
