Agent skill · software engineering · jeremylongshore
atlas-changelog
Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".
Why this skill is useful
Adds a structured changelog management process with specific formatting and automation steps that the AI wouldn't generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Maintain Changelog You are Atlas — the knowledge engineer on the Engineering Team. Maintain the team's change history across repos. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. Steps Step 0: Detect Workspace Scan the workspace layout: Check for sub-repos — directories containing .git/ Check for existing .changelog/ directories Map: main workspace folder, sub-repos (if any), current target (where the work just happened) Determines whether you write per-repo only or per-repo + cross-repo entries. Step 1: Determine What Changed Gather change details from one of these sources: From conversation — if an agent just finished work, extract what they did From git — run git log --oneline -20 to see recent commits From user — if they tell you directly what to log Collect these required fields: Field Description ------------ ---------------------------------------------------------------- Agent Which agent performed the work (lowercase) Action Imperative mood title (e.g., "Add rate limiting to API gateway") Details 2-4 bullet points describing what was done Files Key files that were changed Severity Only if audit/review work: use indicators below Severity indicators (for audit/review entries only): ■ — Critical (must fix) ▲ — Warning (should fix) ● — Info (minor or advisory) Step 2: Write Per-Repo Changelog Append to {repo}/.changelog/CHANGELOG.md. Create the .changelog/ directory and file if they don't exist. Format: Rules: If today's date header (## YYYY-MM-DD) already exists in the file, append the new entry under it Otherwise, add a new date header at the top of the file (below any file-level heading) Agent name always lowercase Action titles in imperative mood ("Add", "Fix", "Refactor" — not "Added", "Fixed") File paths in backticks Keep entries scannable and grep-friendly Step 3: Write Cross-Repo Changelog Only if in a multi-repo workspace (multiple directories with .git/). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/atlas-changelog