Stats
Actions
Tags
From write-goal
Compile an agent-optimized changelog by cross-referencing git history with plans and documentation. Use when asked to "update changelog", "compile history", "document project evolution", or proactively after major milestones, architectural changes, or when stale/deprecated information is detected that could confuse coding agents.
How this skill is triggered — by the user, by Claude, or both
Slash command
/write-goal:agent-changelogThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Compile a chronological record of key decisions, architectural changes, and project evolution optimized for coding agent context-building.
Compile a chronological record of key decisions, architectural changes, and project evolution optimized for coding agent context-building.
Write to AGENT_CHANGELOG.md in the project root. This file helps agents:
Collect information from these sources in parallel:
Git history:
git log --oneline --since="6 months ago" | head -100
git log --all --oneline --grep="BREAKING" --grep="deprecate" --grep="remove" --grep="migrate" -i
git tag -l --sort=-creatordate | head -20
Documentation:
.claude/plans/ - implementation plans and decisionsCLAUDE.md - project instructionsREADME.md - project overviewdocs/ or similar documentation directoriesCHANGELOG.md if exists (traditional changelog)Code signals:
@deprecated annotationsTODO, FIXME, HACK comments with datesExtract events that matter for agent understanding:
Always include:
Include if significant:
Skip:
For each significant event, check if existing documentation contradicts it:
Event: "Migrated from Redux to Zustand" (commit abc123, 2024-03)
Check: Does any documentation still reference Redux patterns?
- README.md mentions Redux? → Flag as STALE
- CLAUDE.md suggests Redux approach? → Flag as STALE
- Old tutorials in docs/? → Flag as STALE
Track contradictions in a "Stale Information Detected" section.
Structure the output file:
# Agent Changelog
> This file helps coding agents understand project evolution, key decisions,
> and deprecated patterns. Updated: [DATE]
## Current State Summary
[2-3 sentences on where the project is NOW - the authoritative current architecture]
## Stale Information Detected
[List any documentation that contradicts current reality - agents should ignore these until fixed]
| Location | States | Reality | Since |
|----------|--------|---------|-------|
| docs/auth.md | "Uses JWT tokens" | Migrated to sessions | 2024-06 |
## Timeline
### [YEAR-MONTH] - [Brief Title]
**What changed:** [Factual description]
**Why:** [Decision rationale if known from plans/commits]
**Agent impact:** [How this affects how agents should work in the codebase]
**Deprecated:** [What approaches/patterns should agents avoid]
---
[Repeat for each significant event, reverse chronological]
## Deprecated Patterns
[Consolidated list of things agents should NOT do, with what to do instead]
| Don't | Do Instead | Deprecated Since |
|-------|------------|------------------|
| Use `OldService` | Use `NewService` | 2024-08 |
## Trajectory
[Brief note on where the project appears to be heading based on recent changes and plans]
After writing:
AGENT_CHANGELOG.md if present and merge, don't duplicateSuggest running this skill when:
.claude/plans/ were recently executedProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub petekp/agent-skills --plugin rust