jeremylongshore/tons-of-skills-marketplace / plugins/devops/mattyp-changelog/skills/changelog-orchestrator
changelog-orchestrator
VerifiedDraft 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".
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.jsonin the target repo. - Required environment variables set (at minimum
GITHUB_TOKENfor GitHub source). - Git available in PATH;
ghoptional (used for PR creation if configured).
Instructions
- Read
.changelog-config.jsonfrom 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) andversion(SemVer if known; otherwise0.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 withdocs: add changelog for YYYY-MM-DD. - If
ghis 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
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |