Skill

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".

npx claudepluginhub flight505/skill-forge --plugin mattyp-changelog

Tool Access

This skill is limited to using the following tools:

ReadWriteEditGrepGlobBash(git:*)Bash(gh:*)Bash(python:*)Bash(date:*)

Preview

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.

Supporting Assets

assets/default-changelog.mdassets/release-template.mdassets/weekly-template.mdreferences/errors.mdreferences/examples.mdreferences/implementation.mdscripts/quality_score.pyscripts/render_template.pyscripts/validate_config.py

SKILL.md

Similar Skills

using-superpowers

180.9k

Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.

3 files

superpowers

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 30, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

changelog-orchestrator

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

Read .changelog-config.json from the repo root.

Validate it with ${CLAUDE_SKILL_DIR}/scripts/validate_config.py.

Decide date range:

Load the configured markdown template (or fall back to ${CLAUDE_SKILL_DIR}/assets/weekly-template.md).

Render the final markdown using ${CLAUDE_SKILL_DIR}/scripts/render_template.py.

Ensure frontmatter contains at least date (ISO) and version (SemVer if known; otherwise 0.0.0).

Run deterministic checks using ${CLAUDE_SKILL_DIR}/scripts/quality_score.py.

If score is below threshold:

Write the changelog file to the configured output_path.

Create a branch changelog-YYYY-MM-DD, commit with docs: add changelog for YYYY-MM-DD.

If gh is configured, open a PR; otherwise, print the exact commands the user should run.

See ${CLAUDE_SKILL_DIR}/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 ${CLAUDE_SKILL_DIR}/scripts/quality_score.py.

Error Handling

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

Examples

See ${CLAUDE_SKILL_DIR}/references/examples.md for detailed examples.

Resources

Validate config: ${CLAUDE_SKILL_DIR}/scripts/validate_config.py

Render template: ${CLAUDE_SKILL_DIR}/scripts/render_template.py

Quality scoring: ${CLAUDE_SKILL_DIR}/scripts/quality_score.py

Default templates:

${CLAUDE_SKILL_DIR}/assets/default-changelog.md
${CLAUDE_SKILL_DIR}/assets/weekly-template.md
${CLAUDE_SKILL_DIR}/assets/release-template.md