home / skills / linehaul-ai / linehaulai-claude-marketplace / wiki-changelog

wiki-changelog skill

/plugins/deep-wiki/skills/wiki-changelog

This skill analyzes git history and generates structured changelogs categorized by change type for easy understanding of recent repository activity.

npx playbooks add skill linehaul-ai/linehaulai-claude-marketplace --skill wiki-changelog

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.7 KB

---
name: wiki-changelog
description: 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.
---

# 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:

1. **Check for git remote**: Run `git remote get-url origin` to detect if a remote exists
2. **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
3. **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

1. Examine git log (commits, dates, authors, messages)
2. Group by time period: daily (last 7 days), weekly (older)
3. Classify each commit: Features (🆕), Fixes (🐛), Refactoring (🔄), Docs (📝), Config (🔧), Dependencies (📦), Breaking (⚠️)
4. 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)`

Overview

This skill analyzes a Git commit history and generates structured, user-focused changelogs categorized by change type. It produces concise descriptions, groups commits by recent time periods, and highlights breaking changes with migration notes. It links commits and files to the source repository when a remote URL is available.

How this skill works

First, the skill resolves the source repository context by detecting a git remote or asking the user for a repository URL. It then inspects the git log (commits, dates, authors, messages) and groups activity by time period (daily for the last 7 days, weekly for older). Commits are classified into categories like Features, Fixes, Refactoring, Docs, Config, Dependencies, and Breaking. Related commits are merged into coherent user-facing descriptions and, if a REPO_URL is provided, commit hashes and file paths are emitted as links.

When to use it

When a user asks “what changed recently” or “summarize commits”
Before releases to generate a human-readable changelog
When auditing recent development activity or onboarding reviewers
When preparing release notes or highlighting breaking changes
To convert raw commit history into user-facing change categories

Best practices

Always resolve repository context first: detect git remote or ask for a repo URL
Focus descriptions on user-facing impact rather than implementation details
Merge related commits into single changelog entries to avoid noise
Prominently surface breaking changes and include migration notes
Use project terminology from the codebase README for clarity

Example use cases

Generate a release changelog for the past two weeks, grouped by Features/Fixes/Docs
Summarize last 7 days of work for stakeholders with daily grouping
Identify all breaking changes since the previous release and produce migration steps
Create a dependency-upgrade section listing upgraded packages and potential impacts
Produce file-linked commit citations when given a GitHub or similar repo URL

FAQ

What do you need before generating a changelog?

I must determine the source repository context. I will check for a git remote and ask whether this is local-only or provide a repository URL. I will not proceed until that is resolved.

Can commit hashes and file paths be linked?

Yes. If you provide a remote repository URL (for example GitHub), I will emit linked citations for commit hashes and changed file paths using that URL.