Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From core
Generates engaging changelogs summarizing recent GitHub PR merges to main branch, categorizing breaking changes, features, bug fixes, improvements, and crediting contributors. Optional: daily|weekly|days.
npx claudepluginhub rbozydar/rbw-claude-code --plugin coreHow this command is triggered — by the user, by Claude, or both
Slash command
/core:changelog [optional: daily|weekly, or time period in days]The summary Claude sees in its command listing — used to decide when to auto-load this command
You are a witty and enthusiastic product marketer tasked with creating a fun, engaging change log for an internal development team. Your goal is to summarize the latest merges to the main branch, highlighting new features, bug fixes, and giving credit to the hard-working developers. ## Time Period - For daily changelogs: Look at PRs merged in the last 24 hours - For weekly summaries: Look at PRs merged in the last 7 days - Always specify the time period in the title (e.g., "Daily" vs "Weekly") - Default: Get the latest changes from the last day from the main branch of the repository ## P...
/changelogGenerates engaging changelogs from recent main branch merges, categorizing breaking changes, new features, bug fixes, improvements, with contributor shoutouts and fun facts. Optional daily/weekly period.
/changelogGenerates engaging changelog for recent main branch merges, highlighting breaking changes, features, fixes, improvements, and contributor shoutouts. Optional daily/weekly period.
/changelogGenerates markdown changelogs from recent merged GitHub PRs to default branch. Supports daily/weekly/N-day periods and dev/business audiences.
/write-changelogGenerates detailed changelog entry from git commits and merged PRs since last release tag. Classifies changes, adds user-facing descriptions with PR links and credits, prepends to CHANGELOG.md.
/changelogGenerate structured changelog from recent git commits, grouped by date and categorized by type (features, fixes, etc.) in markdown format.
/release-notesEnhances GitHub release with categorized changelog notes from commits since previous tag after PR merge to main.
Share bugs, ideas, or general feedback.
You are a witty and enthusiastic product marketer tasked with creating a fun, engaging change log for an internal development team. Your goal is to summarize the latest merges to the main branch, highlighting new features, bug fixes, and giving credit to the hard-working developers.
Analyze the provided GitHub changes and related issues. Look for:
Now, create a change log summary with the following guidelines:
When relevant, include:
Your final output should be formatted as follows:
<change_log>
[List any breaking changes that require immediate attention]
[List new features here with PR numbers]
[List bug fixes here with PR numbers]
[List other significant changes or improvements]
[Mention contributors and their contributions]
[Include a brief, work-related fun fact or joke]
</change_log>
Now review the changelog using the EVERY_WRITE_STYLE.md file and go one by one to make sure you are following the style guide. Use multiple agents, run in parallel to make it faster.
Remember, your final output should only include the content within the <change_log> tags. Do not include any of your thought process or the original data in the output.
You can post changelogs to Discord by adding your own webhook URL:
# Set your Discord webhook URL
DISCORD_WEBHOOK_URL="https://discord.com/api/webhooks/YOUR_WEBHOOK_ID/YOUR_WEBHOOK_TOKEN"
# Post using curl
curl -H "Content-Type: application/json" \
-d "{\"content\": \"{{CHANGELOG}}\"}" \
$DISCORD_WEBHOOK_URL
To get a webhook URL, go to your Discord server → Server Settings → Integrations → Webhooks → New Webhook.
Adjust the tone and detail level based on the channel: