skills.rest
petekp
petekpCOMMUNITY
Explore all skills by this author →
Website𝕏@petekpGitHub

agent-changelog

Compile an agent-focused changelog by cross-referencing git history, plans, and documentation.

5|2|Updated Jan 20, 2026
Search Tags:#planning#changelog#architecture#documentation#codebase#git-history
One-click install
npx skills add https://github.com/petekp/agent-skills --skill agent-changelog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-changelog
Source: https://github.com/petekp/agent-skills/tree/main/skills/agent-changelog
Command: npx skills add https://github.com/petekp/agent-skills --skill agent-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compile a chronological changelog by cross-referencing git history with plans and documentation to keep coding agents informed about project evolution.

Core Features & Use Cases

  • Cross-reference git history, plans, and docs to surface key decisions, migrations, and deprecated patterns.
  • Generate AGENT_CHANGELOG.md at project root with architectural changes, rationale, and trajectory.
  • Provide a reference that helps agents avoid stale information and misaligned expectations.

Quick Start

Run the changelog workflow to generate AGENT_CHANGELOG.md from the listed sources.

Frequently Asked Questions about agent-changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a changelog from git history and project documentation?▼

Generate a changelog from git history and project documentation by cross-referencing commits with plans and docs. This compiles architectural decisions and breaking changes into a chronological AGENT_CHANGELOG.md file at your project root.

What is an agent-focused changelog and why do I need one for my codebase?▼

An agent-focused changelog is a chronological record of architectural changes and project evolution. It keeps coding agents informed about decisions and migrations, preventing them from relying on stale information or misaligned expectations.

Can I compile a changelog using plans from .claude/plans and CLAUDE.md files?▼

Yes, you can compile a changelog using plans from .claude/plans and CLAUDE.md files. The process cross-references these documentation sources with git history to surface key decisions, deprecations, and project trajectory.

Do I need six months of git history to generate an architectural changelog?▼

Yes, six months of git history is required to generate an architectural changelog. This duration provides sufficient commit data to accurately identify project evolution, breaking changes, and deprecated patterns.

What's the best way to document architectural decisions and breaking changes for coding agents?▼

The best way to document architectural decisions and breaking changes for coding agents is generating an AGENT_CHANGELOG.md file. It cross-references git history with plans and docs to provide a clear trajectory of project evolution.

Why does my coding agent use outdated patterns after recent codebase migrations?▼

Coding agents use outdated patterns when they lack a compiled changelog of recent migrations. Generating an AGENT_CHANGELOG.md cross-references git history and documentation to prevent agents from referencing stale information.

Related Skills

Explore More Software Engineering Skills→
t6adevt6adev
3

doc-sync

Detect documentation drift from git history and propose edits to project docs.

Community
Intermediate
tae2089tae2089
2

persona-agent-team-planner

Route agent-team workflow planning through terminology alignment and architecture design.

Community
Intermediate
tsuna44tsuna44

xddp.fill-rulebook

Generate project-rulebook documentation from repository structure and git history.

Community
Advanced
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate