project-orchestrator:changelog
Use when completing changes to any service - ensures standardized changelog entries with correct format, location, and content.
Best use case
project-orchestrator:changelog is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when completing changes to any service - ensures standardized changelog entries with correct format, location, and content.
Teams using project-orchestrator:changelog should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/project-orchestrator-changelog/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How project-orchestrator:changelog Compares
| Feature / Agent | project-orchestrator:changelog | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when completing changes to any service - ensures standardized changelog entries with correct format, location, and content.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Changelog
## Overview
Write standardized changelog entries after completing changes. Focus on WHY not WHAT.
## Config Loading
1. Check if `.project-orchestrator/project.yml` exists
2. If yes: use `config.services[name].changelog` for the correct file path
3. If no: look for `CHANGELOG.md` in the service directory or project root
## When to Trigger
After completing:
- Bug fixes
- New features
- Refactors affecting behavior
- API changes
- Configuration changes
**Skip for:** typo fixes, comment-only changes, test-only changes
## Format
```markdown
### YYYY-MM-DD - Brief Title
**Summary:** One-line description.
**What prompted the change:**
- Motivation or problem
**Problem solved:**
- What this enables
```
## Location
Write to the affected service's changelog path from `config.services[name].changelog`.
If no changelog path is configured:
- Check if `{service_path}/CHANGELOG.md` exists
- If not, check if `CHANGELOG.md` exists at project root
- If neither exists, ask the user where to write the entry
**Multiple services?** Write entry to EACH affected service's changelog.
## Checklist
- [ ] Date format: YYYY-MM-DD (not "Jan 17")
- [ ] Title: Brief, describes outcome (not implementation)
- [ ] Summary: One line, WHY not WHAT
- [ ] Prompted: What problem existed
- [ ] Solved: What's now possible
- [ ] 10-20 lines max
- [ ] Written to correct service changelog
## Red Flags
| Bad | Good |
|-----|------|
| "Updated code" | "Fix bookmark sync failing silently" |
| "Fixed bug" | "Prevent duplicate records on import" |
| Lists files changed | Explains behavior change |
| 50+ lines | 10-20 lines |
| Entry in root README | Entry in service CHANGELOG.md |
## Example
```markdown
### 2026-01-17 - Fix SSE reconnection dropping notifications
**Summary:** SSE connections now preserve undelivered notifications during reconnect.
**What prompted the change:**
- Users reported missing notifications after connection drops
**Problem solved:**
- Notifications queue during disconnect and deliver on reconnect
```Related Skills
wiki-changelog
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 th...
store-changelog
Generate release notes for app stores (Android Play Store, iOS App Store, macOS App Store, Linux Flatpak). Use when the user asks for changelogs, release notes, or store descriptions based on git history.
review-changelog
Review and complete new changelog entries after automated PR creation. Use when there's a new changelog PR with entries that have placeholder URLs or empty fields that need review. Triggers on phrases like "review changelog", "complete changelog entries", "fix changelog PR", or when user mentions a PR with changelog updates.
changelogator
Generate a changelog from git commits. Use when the user asks to generate a changelog, prepare release notes, summarize commits, prepare a release, suggest a version bump, or review changes since last tag. Also use when the user mentions "changelog", "release notes", "what changed", "version bump", or "semver".
changelog-update
Update CHANGELOG.md [Unreleased] section with business-focused entries via systematic file review
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
changelog
Write changelog entries for Hugging Face Hub features. Use when asked to write a changelog, create a changelog entry, or document a new feature/PR for hf.co/changelog. Triggers on "write changelog", "changelog entry", "document this PR/feature for changelog".
changelog-automation
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
archon-project
Gestion du projet MyGGV GPS dans Archon. Utiliser pour la documentation, les tâches, la recherche dans la knowledge base (Supabase docs, MapLibre docs, etc.), et le suivi de projet.
app-store-changelog
Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.
analyze-project
Analyze a project's codebase and documentation to generate coding standards, architecture docs, and development practices. Perfect for new project onboarding. Usage: 'analyze-project: /path/to/project' or 'analyze: /path/to/project'
agent-changelog
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.