---
title: "ship-ready"
description: "Release-readiness copilot: go/no-go checks, semver suggestions, changelog drafts, and guardrails for risky release commands."
canonical: https://agentpluginsdirectory.com/plugins/ship-ready--sekar3s
last-updated: 2026-10-25
---

# ship-ready
Release-readiness copilot: go/no-go checks, semver suggestions, changelog drafts, and guardrails for risky release commands.
- Slug: ship-ready--sekar3s
- Publisher: OctoCAT Platform Team
- Repository: https://github.com/sekar3s/octocat-agent-plugins-demo
- Manifest: plugins/ship-ready/plugin.json
- Version: 1.0.0
- License: MIT
- Category (editorial): other
- Skills: 1 (release-readiness)
- MCP servers: 1 (release-radar)
- Stars: 0
- Repository created: 2026-09-29
- Repository last pushed: 2026-10-14
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/ship-ready--sekar3s
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What ship-ready does, in the publisher's words

Release-readiness copilot. Decide Go/No-Go with evidence, get a semantic version recommendation and a draft changelog, and add guardrails around risky release commands in every Copilot client.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/sekar3s/octocat-agent-plugins-demo/HEAD/plugins/ship-ready/README.md

## Skills

- release-readiness: Assess whether a repository is ready to release and produce a Go/No-Go report with a suggested semantic version and draft changelog. Use when the user asks "are we ready to ship/release?", wants a release checklist, a version bump recommendation, release notes, or a changelog before tagging or publ…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- release-radar: transport: stdio; command: node ${PLUGIN_ROOT}/servers/release-radar.mjs

Read from the plugin's own mcp.json. Environment variable names only, never values.