project-orchestrator:changelog

What problem does it solve?

Service changes often fail to produce consistent changelog entries across multiple services, leading to brittle release notes and documentation gaps. This Skill enforces a standardized format, ensures entries are written to the correct locations, and captures essential metadata (date, title, rationale).

Core Features & Use Cases

• Centralized formatting: writes changelog entries in a consistent structure for all affected services.
• Flexible location: respects per-service paths via the configured changelog field or falls back to CHANGELOG.md in the service or project root.
• Scope-aware: supports single or multi-service changes and writes to each affected service's changelog.

Quick Start

Run the changelog update after completing changes to a service to generate a properly formatted entry.