Wiki Changelog
Generate structured changelogs from git history.
Source Repository Resolution (MUST DO FIRST)
Before generating any changelog, you MUST determine the source repository context:
- Check for git remote: Run
git remote get-url origin to detect if a remote exists
- Ask the user: "Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?"
- Remote URL provided → store as
REPO_URL, use linked citations for commit hashes and file references
- Local-only → use plain commit hashes and file references
- Do NOT proceed until source repo context is resolved
When to Activate
- User asks "what changed recently", "generate a changelog", "summarize commits"
- User wants to understand recent development activity
Procedure
- Examine git log (commits, dates, authors, messages)
- Group by time period: daily (last 7 days), weekly (older)
- Classify each commit: Features (🆕), Fixes (🐛), Refactoring (🔄), Docs (📝), Config (🔧), Dependencies (📦), Breaking (⚠️)
- Generate concise user-facing descriptions using project terminology
Constraints
- Focus on user-facing changes
- Merge related commits into coherent descriptions
- Use project terminology from README
- Highlight breaking changes prominently with migration notes
- When
REPO_URL is available, link commit hashes: [abc1234](REPO_URL/commit/abc1234) and changed files: [file_path](REPO_URL/blob/BRANCH/file_path)
When to Use
Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in the repository.
Covers: Source Repository Resolution (MUST DO FIRST), When to Activate, Procedure, Constraints.
1---2name: wiki-changelog3description: Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in the repository.4license: MIT5---6# Wiki Changelog78Generate structured changelogs from git history.910## Source Repository Resolution (MUST DO FIRST)1112Before generating any changelog, you MUST determine the source repository context:13141. **Check for git remote**: Run `git remote get-url origin` to detect if a remote exists152. **Ask the user**: _"Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?"_16 - Remote URL provided → store as `REPO_URL`, use **linked citations** for commit hashes and file references17 - Local-only → use plain commit hashes and file references183. **Do NOT proceed** until source repo context is resolved1920## When to Activate2122- User asks "what changed recently", "generate a changelog", "summarize commits"23- User wants to understand recent development activity2425## Procedure26271. Examine git log (commits, dates, authors, messages)282. Group by time period: daily (last 7 days), weekly (older)293. Classify each commit: Features (🆕), Fixes (🐛), Refactoring (🔄), Docs (📝), Config (🔧), Dependencies (📦), Breaking (⚠️)304. Generate concise user-facing descriptions using project terminology3132## Constraints3334- Focus on user-facing changes35- Merge related commits into coherent descriptions36- Use project terminology from README37- Highlight breaking changes prominently with migration notes38- When `REPO_URL` is available, link commit hashes: `[abc1234](REPO_URL/commit/abc1234)` and changed files: `[file_path](REPO_URL/blob/BRANCH/file_path)`3940## When to Use4142Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in the repository.4344Covers: Source Repository Resolution (MUST DO FIRST), When to Activate, Procedure, Constraints.
JantonioFC