SaturdayMP Claude Plugins

A Claude Code Marketplace plugins that Saturday Morning Productions finds useful and hope you do as well.

Prerequisites

• Claude Code CLI installed

Installation

From GitHub

Add this repo as a plugin marketplace:

/plugin marketplace add saturdaymp/claude-plugins

From a local clone

Clone the repo:

git clone https://github.com/saturdaymp/claude-plugins.git

Load the local marketplace:

/plugin marketplace add /path/to/cloned/repo

Plugins

Each plugin is published on two release channels:

• Stable (e.g. smp-github): pinned to the most recent release tag, updated only when a release is published.
• Latest (e.g. smp-github-latest): tracks the main branch, updated on every commit.

Install the channel you want:

/plugin install smp-github@saturdaymp-claude-plugins
/plugin install smp-github-latest@saturdaymp-claude-plugins

Don't forget to restart Claude Code or try reloading the plugins:

/reload-plugins

Plugins Available

Plugin	Channels	Description
smp-github	smp-github, smp-github-latest	GitHub workflow skills — see below

Each plugin's README describes its skills in detail. The smp-github plugin provides:

• smp-apply-github-pr-feedback — evaluate a PR review comment, fix it if valid, commit, reply, and resolve the conversation.
• smp-create-gh-changelog-script — create a standalone bash script that generates a CHANGELOG.md from GitHub releases.

Versioning and Releases

This repo uses GitVersion (see GitVersion.yml): the next release version is one minor bump past the most recent release tag, no matter how many PRs have merged since. To bump differently, include +semver: major or +semver: patch in a commit message on main.

Stable channel users only receive updates when the plugin's version and ref in .claude-plugin/marketplace.json change, which the Release workflow handles. Latest channel users receive updates on every commit to main because the latest entries omit version, so each commit SHA counts as a new version. For the same reason, plugin manifests (plugin.json) must not declare a version — it would take precedence over the marketplace entry and pin both channels to the same version.

The Version workflow prints the calculated version in its run summary for every push and pull request to main. To calculate it locally instead:

docker run --rm -v "$PWD:/repo" gittools/gitversion:6.3.0 /repo

Releasing

Run the Release workflow from the GitHub Actions tab. It:

1. Calculates the next version with GitVersion.
2. Tags main with vX.Y.Z and creates a GitHub release with generated notes.
3. Points the stable channel entries in marketplace.json at the new tag.
4. Regenerates CHANGELOG.md, commits both files to a release/vX.Y.Z branch, then opens a PR to main and merges it with a merge commit (the branch ruleset requires changes via pull request).

Generating the Changelog

Run the script to generate or update CHANGELOG.md from GitHub releases:

./scripts/generate-changelog.sh              # Writes to CHANGELOG.md
./scripts/generate-changelog.sh docs/CHANGES.md  # Custom output path

Requirements: GitHub CLI (gh) installed and authenticated.

This script was generated by the smp-create-gh-changelog-script skill from this repo's own smp-github plugin.

License

MIT