> 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".
curl "https://skillshub.wtf/jeremylongshore/claude-code-plugins-plus-skills/changelog-orchestrator?format=md"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 --same-repo
> fathom-cost-tuning
Optimize Fathom API usage and plan selection. Trigger with phrases like "fathom cost", "fathom pricing", "fathom plan".
> fathom-core-workflow-b
Sync Fathom meeting data to CRM and build automated follow-up workflows. Use when integrating Fathom with Salesforce, HubSpot, or custom CRMs, or creating automated post-meeting email summaries. Trigger with phrases like "fathom crm sync", "fathom salesforce", "fathom follow-up", "fathom post-meeting workflow".
> fathom-core-workflow-a
Build a meeting analytics pipeline with Fathom transcripts and summaries. Use when extracting insights from meetings, building CRM sync, or creating automated meeting follow-up workflows. Trigger with phrases like "fathom analytics", "fathom meeting pipeline", "fathom transcript analysis", "fathom action items sync".
> fathom-common-errors
Diagnose and fix Fathom API errors including auth failures and missing data. Use when API calls fail, transcripts are empty, or webhooks are not firing. Trigger with phrases like "fathom error", "fathom not working", "fathom api failure", "fix fathom".