changelog-orchestrator

Draft changelog PRs by collecting GitHub/Slack/Git changes, formatting with templates, running quality gates, and preparing a branch/PR. Use when generating weekly/monthly release notes or when the user asks to create a changelog from recent merges. Trigger with "changelog weekly", "generate release notes", "draft changelog", "create changelog PR".

⭐878stars🔀101forks📁View on GitHub🕐Updated Jan 4, 2026⬇️3downloads

When & Why to Use This Skill

The Changelog Orchestrator is a specialized Claude skill designed to automate the end-to-end process of generating release notes. By aggregating data from GitHub, Git commits, and Slack updates, it transforms raw repository activity into professional, template-based changelogs. It enhances developer productivity by performing automated quality checks and streamlining the workflow through automatic branch creation and Pull Request drafting.

Use Cases

  • Weekly/Monthly Release Summaries: Automatically gather all merged PRs and significant commits over a specific timeframe to create comprehensive release notes for stakeholders.
  • Automated Documentation Maintenance: Keep the CHANGELOG.md file up-to-date by having the agent identify recent changes, format them according to project standards, and open a PR for review.
  • Cross-Platform Activity Aggregation: Consolidate technical updates from GitHub with contextual discussions from Slack to ensure no critical feature or fix is missed in the public log.
  • Quality-Gated Documentation: Ensure all changelog entries meet specific quality scores and formatting standards before they are committed to the repository, maintaining a high standard for project documentation.
namechangelog-orchestrator
descriptionDraft changelog PRs by collecting GitHub/Slack/Git changes, formatting with templates, running quality gates, and preparing a branch/PR. Use when generating weekly/monthly release notes or when the user asks to create a changelog from recent merges. Trigger with "changelog weekly", "generate release notes", "draft changelog", "create changelog PR".
allowed-tools"Read, Write, Edit, Grep, Glob, Bash(git:*), Bash(gh:*), Bash(python:*), Bash(date:*)"
version"0.1.0"
author"Mattyp <mattyp@claudecodeplugins.io>"
license"MIT"

Changelog Orchestrator

Overview

This skill turns raw repo activity (merged PRs, issues, commits, optional Slack updates) into a publishable changelog draft and prepares a branch/PR for review.

Prerequisites

  • A project config file at .changelog-config.json in the target repo.
  • Required environment variables set (at minimum GITHUB_TOKEN for GitHub source).
  • Git available in PATH; gh optional (used for PR creation if configured).

Instructions

  1. Read .changelog-config.json from the repo root.
  2. Validate it with {baseDir}/scripts/validate_config.py.
  3. Decide date range:
  4. Load the configured markdown template (or fall back to {baseDir}/assets/weekly-template.md).
  5. Render the final markdown using {baseDir}/scripts/render_template.py.
  6. Ensure frontmatter contains at least date (ISO) and version (SemVer if known; otherwise 0.0.0).
  7. Run deterministic checks using {baseDir}/scripts/quality_score.py.
  8. If score is below threshold:
  9. Write the changelog file to the configured output_path.
  10. Create a branch changelog-YYYY-MM-DD, commit with docs: add changelog for YYYY-MM-DD.
  11. If gh is configured, open a PR; otherwise, print the exact commands the user should run.

See {baseDir}/references/implementation.md for detailed implementation guide.

Output

  • A markdown changelog draft (usually CHANGELOG.md), plus an optional PR URL.
  • A quality report (score + findings) from {baseDir}/scripts/quality_score.py.

Error Handling

See {baseDir}/references/errors.md for comprehensive error handling.

Examples

See {baseDir}/references/examples.md for detailed examples.

Resources

  • Validate config: {baseDir}/scripts/validate_config.py
  • Render template: {baseDir}/scripts/render_template.py
  • Quality scoring: {baseDir}/scripts/quality_score.py
  • Default templates:
    • {baseDir}/assets/default-changelog.md
    • {baseDir}/assets/weekly-template.md
    • {baseDir}/assets/release-template.md