git-storytelling-commit-strategy

# Git Storytelling - Commit Strategy

This skill helps you understand and implement effective commit strategies that tell the story of your development process through small, focused commits.

## Key Concepts

### Commit Early, Commit Often

The practice of making small, frequent commits throughout development rather than large, infrequent commits. This approach:

- Creates a detailed history of your thought process
- Makes it easier to understand changes
- Simplifies debugging and reverting changes
- Enables better code reviews
- Tells the story of how the solution evolved

### Atomic Commits

Each commit should represent a single logical change:

- One feature addition
- One bug fix
- One refactoring
- One documentation update

This makes the git history navigable and meaningful.

### The Story Arc

Your commits should read like a story:

1. **Setup**: Initial project structure, dependencies
2. **Development**: Incremental feature additions
3. **Refinement**: Bug fixes, optimizations
4. **Polish**: Documentation, cleanup

## Best Practices

### DO Commit When

✅ You've completed a logical unit of work (even if small)
✅ Tests pass for the changes made
✅ You're about to switch tasks or take a break
✅ You've refactored code to be clearer
✅ You've fixed a bug (one commit per bug)
✅ You've added a new file or module
✅ You've updated documentation
✅ You're at a stable checkpoint

### DON'T Commit When

❌ Code doesn't compile or has syntax errors
❌ Tests are failing (unless documenting a known issue)
❌ You have unrelated changes mixed together
❌ You have debugging code or temporary comments
❌ You have secrets or sensitive data

## Commit Message Patterns

### Good Commit Messages

```
feat: add user authentication with JWT

Implement JWT-based authentication system with:
- Login endpoint
- Token generation
- Token validation middleware

🤖 Generated with [Claude Code](https://claude.com/claude-code)

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

```
fix: resolve me