tonone-ai/tonone / bundle/engineering-team/skills/atlas-changelog
atlas-changelog
VerifiedMaintain 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".
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 -20to 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:
## {YYYY-MM-DD}
### {agent} — {action title}
- {detail bullet}
- {detail bullet}
- Files: `path/to/file.py`, `path/to/other.py`
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/).
Append to {workspace}/.changelog/CHANGELOG.md. Create if it doesn't exist.
Format:
## {YYYY-MM-DD}
### {repo-name}
- {agent} — {action title one-liner}
Rules:
- Group entries by repo under each date header
- One-line summaries only — no detail bullets
- If today's date header exists, append under the correct repo section or add a new repo section
- Create the file if it doesn't exist
Step 4: Write Per-Agent Activity Log
Append to team/{agent}/.activity.md in the tonone plugin directory.
Format:
## {YYYY-MM-DD HH:MM} — {repo-name}
**Action:** {what was done}
**Skill:** {skill-name}
**Files:** {N} modified, {N} created
**Verdict:** {severity summary or "Complete"}
Rules:
- Use 24-hour timestamp
- Use the repo directory name, not the full path
- Create
.activity.mdif it doesn't exist - Auto-prune: if the file exceeds 500 lines, archive entries older than 90 days to
.activity-archive.mdin the same directory
Step 5: Present CLI Summary
╭─ ATLAS ── atlas-changelog ──────────────────╮
## Changelog updated
### Entries Written
→ {repo}/.changelog/CHANGELOG.md
→ .changelog/CHANGELOG.md (workspace)
→ team/{agent}/.activity.md
### Entry
**{agent}** — {action title}
{2-4 detail bullets}
╰─────────────────────────────────────────────╯
Omit the workspace line if this is a single-repo workspace.
Key Rules
- Never overwrite — always append to existing files
- Date headers use
## YYYY-MM-DDformat only - Per-repo changelogs have full details; cross-repo changelogs have one-liners
- Archive activity log entries older than 90 days when file exceeds 500 lines
- Changelog entries should be committed with the work they describe
- If unclear what changed, ask — don't guess
Delivery
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |