2,935 mods in this category, of every kind an
agent can take. Each one carries what it costs per session, what the
scan found, and whether it is the original.
Generate a concise, user-facing changelog from meaningful changes in the current repository and branch. Use when the user asks for a changelog, release notes, recent changes, or a summary of work over a date range or contributor scope.
A workflow for publishing a new version of the agent-skills repository using version tags and a GitHub Release. It reviews commits since the last tag, proposes a semantic version change, updates the changelog, and publishes the release.
Prepare a versioned release or Claude Code marketplace catalog state tag: update release files, create a release commit, tag locally, and optionally publish a GitHub Release.
★not rated 2 1mo agoA
tokens not measured
originalMIT
Coordinate software release preparation, rollout readiness, migration notes, rollback planning, stakeholder communication, and final go/no-go release packets. Use when asked to prepare a release packet, review release readiness, or turn scattered launch notes into one reusable release workflow. Do not use for generic…
Fetches recent changelogs from any tools or projects and presents a scannable digest. Defaults to Claude Code, GitHub Copilot, OpenAI Codex, and OpenClaw. Add or remove any source you want.
★not rated 2 5mo agoA
tokens not measured
originalMIT
Complete release and git workflow management. Semantic versioning, branch strategies, and conflict resolution. Use for releases, version management, git-flow setup, or resolving rebase conflicts.
This skill should be used when the user wants to create a new release — bump version, tag, push, create GitHub release, and optionally publish to npm. Use when user says "release", "bump version", "publish", "cut a release", or "release candidate".
Use when the user wants to publish a new release, says "release", "publish release", "cut a release", or "new version". Covers tag creation, CI-driven build, and troubleshooting.
Use an on-premises GitHub CLI MCP server to select an isolated GitHub account and work with allowlisted repositories, committed files, issues, pull requests, checks, Actions logs, releases, labels, milestones, and Projects v2. Use for GitHub inspection, review, contribution, or administration requests that require…
Plain-Markdown Scrum/Agile product management for Claude Code — backlog, sprints, board, velocity, releases, and GitHub traceability from slash commands.
★not rated 1 1mo agoA
tokens not measured
originalMIT
Determine whether the next release is legally a patch, minor, or major by diffing the public API surface against the last published version. Use before cutting a release, when reviewing "is this breaking?", or when writing honest release notes.
A release checklist for research repositories that publish versions with Zenodo, a service that assigns permanent digital object identifiers (DOIs) to research outputs. It also records a Software Heritage identifier, which helps identify archived source code.
Project-local release pipeline — bump version, regenerate CHANGELOG from commits since last tag, update README docs for new features (with concrete examples + argument explanations), commit + tag + push, open a PR if on a non-main branch, then hand off a manual npm publish (no token configured yet).
MUST USE for ANY git operations. Atomic commits, rebase/squash, cherry-pick, worktree, reflog recovery, and history search (blame, bisect, log -S). STRONGLY RECOMMENDED: Use with task(category='quick', loadskills=['git-master'], ...) to save context. Triggers: 'commit', 'rebase', 'squash', 'cherry-pick', 'worktree'…
Release plugins — code review, bump versions, verify consistency, and push to GitHub.
★not rated 1 3mo agoA18 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: