req-ship SKILL.md skillA
req-ship from minimax-ai/mcode-stack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add minimax-ai/mcode-stack/req-ship@git:20261106.633cee9Pins git:20261106.633cee9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- minimax-ai/mcode-stack
- Path
stacks/req-tpm/skills/req-ship/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261106.633cee9, committed Nov 6, 2026
- Size
- 2,820 bytes
- Repository stars
- 717
- License
- MIT
上线前做就绪检查(回滚方案、可观测性、完成定义 DoD),全部有证据后再推进 Meegle 状态或节点。Use before a requirement is deployed or marked done, when someone says 可以上线了吗 / 准备发布, or before transitioning the work item to a released state.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 上线就绪(req-ship) 「代码合了」不等于「可以上线」,更不等于「需求完成」。这一步把上线前必须有的东西逐条对证据,缺一条就不推进状态。 ## 1. 就绪清单 | 项 | 要的证据 | 缺了怎么办 | | --- | --- | --- | | 完成定义(DoD) | design 里的检查点逐条打勾,附 PR、测试输出链接 | 回 design 或实施 | | 回滚方案 | 具体操作(回退版本号、开关名、命令)和谁有权限执行 | 写出来再上 | | 可观测性 | 能看到 intake 预期效果指标的看板或查询,上线前截一次基线 | 先补埋点,否则 outcome 无法验收 | | 影响面通知 | 波及面里列的人或团队已知会(链接) | 提出人去通知 | | 发布窗口 | 时间、负责人 | 和负责人对齐 | 证据看真实输出:CI 是在最终提交上跑的吗?测试有没有被过滤跳过? ## 2. 写回文档 把清单和证据写进「8. 上线记录」。 ## 3. 推进 Meegle 先查这个工作项是状态流还是节点流、当前能去哪里、需要什么必填项: ```bash # 状态流 meegle workflow list-state-transitions --project-key <PK> --work-item-id <ID> --format json meegle workflow list-state-required --project-key <PK> --work-item-id <ID> --state-key <目标状态 key> --format json meegle workflow transition-state --project-key <PK> --work-item-id <ID> --transition-id <transition_id> # 节点流 meegle workflow get-node --project-key <PK> --work-item-id <ID> --format json meegle workflow transition --project-key <PK> --work-item-id <ID> --node-id <节点 key> --action confirm ``` `list-state-required` 默认返回全部必填项;加 `--mode unfinished` 只看还没填的。 流转前把命令和目标状态给提出人看,确认后执行;流转后用 `workitem get` 读回状态。 注意:推进到「已上线」不是「已完成」。关闭留给 `req-outcome`。 ## 输出 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_xxqdnidgefeqod6z/c88fd4c2aa54013b1d9d5302cb3d74dbf4941162c0bee10d1425d61a2a4200e8.json
Then /plugin install req-ship@markdownregistry-xxqdnidgefeqod6z in Claude Code. It installs git:20261106.633cee9, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add minimax-ai/mcode-stack/req-ship@sha256:c88fd4c2aa54013bThe line at the top of this page pins the label git:20261106.633cee9, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_xxqdnidgefeqod6z)
7 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in minimax-ai/mcode-stack/req-ship since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of req-ship from somewhere else? Ask it: where did my req-ship come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Nov 6, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/req-ship/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2820 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
minimax-ai/mcode-stack · 717 stars · license MIT · pushed 2026-11-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xxqdnidgefeqod6z GET https://markdownregistry.com/api/v1/resolve?ref=minimax-ai/mcode-stack/req-ship GET https://markdownregistry.com/api/v1/blob/c88fd4c2aa54013b1d9d5302cb3d74dbf4941162c0bee10d1425d61a2a4200e8
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.