3,659 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.
Update per-package CHANGELOG.md files for a Ratel release. Drafts entries with git-cliff (scoped per package), lets you curate, then writes the CHANGELOGs. Handles both RC entries and GA-graduation collapse (merging X.Y.Z-rc. sections into a single X.Y.Z section). Invoke before tagging a release.
Cut a new Marko release. Reads every PR merged since the last tag, audits their release-notes labels, recommends the next version number with reasoning, and — only after you confirm or override it — runs ./bin/release.sh. Use this skill whenever the user types /release or asks to cut, ship, publish, or tag a release.…
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.
A release checklist for publishing a new version of the Usage4Claude app. It covers collecting changes, writing release documents, updating the version, checking the build, and preparing the commit that starts automatic publishing.
Claude Code instructions for akitaonrails/ai-usagebar, covering claude.md, release checklist — must do all of these, hard invariants — never break these, secret-discipline rules (learned the hard way) and live api smoke discipline.
Claude Code instructions for openwong2kim/wmux, covering language (owner decision, 2026-07-20), skill routing, design system and versioning & release (owner decision, 2026-07-05).
Instructions for ellipticmarketing/modelrelay, covering agent instructions, post-feature testing, git commits, release process (mandatory) and test architecture.
Run this skill from the repository root. Treat the release as a real public publish: verify the current remote state first, keep unrelated user changes out of release commits, and report exactly what was built, pushed, and released.
Use when the user says "release", "cut a release", "ship a new version", "release new version", "do the desktop release", or "tag a release". Computes the next version, generates the changelog, pushes a v-macos tag, and monitors the Codemagic CI build that produces and publishes the macOS desktop release. NEVER builds…
The single command that gets a DashClaw change ON MAIN AND LIVE — it resolves everything blocking production, never defers, and never hands back a checklist. Lands feature branches on main (rebase, gate, merge, push so Vercel deploys), bumps the unified platform+SDK version, and realigns every description of the…
Instructions for opensesh/KARIMO, covering karimo source repository rules, release protocol (mandatory), preferred method: release script, manual release checklist (if not using script) and critical: never move tags after release.
Reviews code diffs, PRs, issue queues, release readiness, commits, pushes, publishing, and project audits. Use when users ask in any language for code review, issue or PR triage, release gates, publishing follow-through, or project audits. Not for debugging root causes or prose review.
Release a new version of CodeMie CLI. Use when user says "release", "create release", "publish version", "bump version and release", or wants to publish a new version to npm. Handles version bumping, git tagging, pushing, and GitHub release creation with automatic version detection from conventional commits.
Discover dependencies and prepare or execute Kitaru core and plugin releases, including version proposals, Kitaru UI selection, release PRs, ordered tag commands, artifact verification, and recovery. Use when a user asks what a release depends on or wants to prepare, cut, publish, verify, or recover a Kitaru, Kitaru…
AGENTS.md instructions for kunchenguid/gh-axi, covering project agent memory, dependency bumps and the lockfile, the sdk-provided update command, release process and installable skill (src/skill.ts → skills/gh-axi/skill.md).
A planning command for preparing a minor software release from the changes made since the previous version tag. A version tag is a Git label marking a released point in the code history.
★not rated 260 yesterdayA45 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: