5,320 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.
Build, sign, and submit a Flutter/iOS app to the App Store Connect — covers Xcode archive/export, code signing (including headless-Mac keychain workarounds), the asc CLI for App Store Connect metadata automation, screenshot handoff, and final review submission. Use when asked to build and upload an iOS app, set up App…
AGENTS.md instructions for CodeAlive-AI/ai-driven-development, covering ai-driven development — development guide, git publishing defaults, when to create tags and releases, requires a new tag/release and does not require a new tag/release.
A set of release instructions for a project containing a Rust workspace, a Tauri desktop app, a web frontend, and an image-generation skill. Tauri packages web applications as desktop apps.
Bump version, build, and release Noah for the current platform. Handles signing keys, version bumps across all config files, testing, committing, pushing, and uploading to GitHub Releases.
Drive the AR.IO Node release process end-to-end — preflight checks, prepare commit, finalize with image SHAs, test docker compose profiles, tag & publish, and post-release cleanup. Use when the user says "cut a release", "prepare release N", "finalize the release", or similar.
This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPIAPITOKEN secret.
Grant b4mad-release-agent what it needs to run semantic-release on a Forgejo repo, install just release/just preflight into that repo's justfile and a short how-to into its AGENTS.md, then print the oc command that runs the release. Use when asked to "enable semantic-release for ", to onboard a repo to the release…
Run Vincent Driessen's git-flow branching model — start feature branches, and (later) finish them, cut releases, and ship hotfixes. Trigger when the user asks to "start a feature," "create a gitflow branch," "kick off feature X," or otherwise wants gitflow workflow operations on a git repository.
Prepare Invokta versioned releases on dedicated release branches with synchronized package metadata, changelog and validation evidence, complete repository gates, and one cohesive commit. Use when asked to prepare, cut, stage, or validate an Invokta release or release candidate.
Bump Claudepot version numbers in lock-step across Cargo.toml, Cargo.lock, package.json, src-tauri/tauri.conf.json, README.md, the web install page, and stub a CHANGELOG section. Runs a quality gate first. Does not commit — leaves changes for review, and documents the tag/push path that follows.
Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
Parse git history and produce or update a CHANGELOG.md following the Keep a Changelog convention. Supports Conventional Commits, basic prefix conventions, and unstructured commit messages. Intelligently categorizes changes, detects breaking changes, links to PRs/issues, and handles both initial generation and…
Rewrite a moraine GitHub release body in the house format — one-sentence pitch, install block, usage-focused "what's new" sections with PR links and optional screenshots, a platform-support table, upgrade notes, and a single deduped auto-generated changelog at the bottom. Use when the user says "/release-notes…
Turn feature requests into review-ready pull requests: issue, implementation, tests, a review-and-fix loop, and docs. Runs locally or on GitHub Actions, and is built for complex brownfield repos. Each week its retrospective reads what you actually merged and proposes improvements to your skill extensions.
★not rated 115
changed yesterdayA
tokens not measured
originalMIT
Execute a Kobato release. Use when the user runs /release or asks to release the project. The first argument is the version to release, the second is the next development version.
Use when releasing a new version of mcpp — bumps version, creates tag, triggers release CI, and monitors until all platforms succeed. Covers the full release checklist to avoid common pitfalls like version string mismatches.
Use when the user asks to release a new version, ship a build, or publish a Skill Zoo release. Also use when a tag push results in Homebrew 404 errors or missing artifact failures.
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", or "merge and push". Proactively suggest when the user says code is ready or asks about deploying.
Validate release readiness with evidence-based go/no-go decisions. Covers go/no-go checklists, smoke test suite design, staged rollout validation, rollback criteria and procedures, and post-deployment verification. Ensures release confidence comes from data, not feelings. Use when: "release ready," "go/no-go," "smoke…
Instructions for gintasz/unigent, covering setup — do this first in any fresh checkout or worktree, core vs. adapter, constitution, validation and releases.
★not rated 104 1mo agoA550 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: