generating-changelog

# Git Changelog Generation

Automatically analyze git commit history and generate comprehensive changelogs following industry-standard formats.

## Auto-Invoke Triggers

This skill automatically activates when:

1. **Editing changelog files**: `CHANGELOG.md`, `CHANGELOG.txt`, `HISTORY.md`
2. **Mentioning keywords**: "changelog", "release notes", "version", "semantic versioning"
3. **Git tagging operations**: Creating or discussing version tags
4. **Release preparation**: Discussing release preparation or deployment

## What This Skill Delivers

When invoked, this skill provides:

### 1. Git History Analysis Report
- Commit range analysis (since last tag or specified range)
- Commit categorization by type (feat, fix, docs, etc.)
- Semantic version bump recommendation (MAJOR, MINOR, PATCH)
- Breaking changes detection
- Author and PR number extraction

### 2. Formatted Changelog
Choose from multiple formats:
- **Keep a Changelog** (default) - Industry standard, human-friendly
- **Conventional** - Follows Conventional Commits specification
- **GitHub** - GitHub-style release notes with PR links

### 3. Update Strategy
- Append to existing CHANGELOG.md (preserves history)
- Overwrite with fresh changelog
- Create new version section
- Merge with existing sections

## Common Use Cases

### Project Types
- **Microservices**: Track changes across multiple services
- **Frontend Applications**: UI updates and features
- **API Development**: REST API versioning and breaking changes
- **Infrastructure**: Deployment, CI/CD, DevOps updates
- **Documentation**: Technical docs, API docs, guides

### Conventional Commit Examples
The skill recognizes standard commit conventions:
```
feat: add new authentication endpoint
fix: resolve token expiration issue
docs: update API documentation
refactor: optimize database queries
perf: improve calculation performance
test: add integration tests
build: upgrade framework version
ci: configure automated testing
chore: update dependencies
```

#