agentsclimarketplace

Changelog orchestrator

Skill jeremylongshore/claude-code-plugins-plus-skills/skills/.curated/changelog-orchestrator

425 plugins, 2,810 skills, 200 agents for Claude Code. Open-source marketplace at tonsofskills.com with the ccpi CLI package manager.

Install
npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill changelog-orchestrator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.8 KB, as published. Nobody here has run it

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 ${CLAUDE_SKILL_DIR}/scripts/validate_config.py.
  3. Decide date range:
  4. Load the configured markdown template (or fall back to ${CLAUDE_SKILL_DIR}/assets/weekly-template.md).
  5. Render the final markdown using ${CLAUDE_SKILL_DIR}/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 ${CLAUDE_SKILL_DIR}/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 ${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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.