一键在 Manus 中运行任何 Skill

ship-pro

星标0

分支0

更新时间2026年7月18日 13:49

Shipping and release readiness workflow for software changes. Inspired by gstack ship workflows and adapted for Codex v4.3. Use when preparing a feature, desktop app, web app, API change, or release for delivery, including final checks, docs, changelog, versioning, rollback, and deployment readiness.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

PAISHU-AI

PAISHU-AI/PAI-zong-NB-v5.8

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Ship Pro

Workflow

Confirm scope: what is shipping and what is not.
Verify code quality: tests, lint, typecheck, build, and relevant manual checks.
Verify docs: .ai_project.md, feature docs, API docs, deployment notes, changelog.
Verify release safety: migrations, env vars, flags, rollback, monitoring, user impact.
Use production-readiness-pro for commercial go/no-go decisions.
Use project-sync-audit to catch stale project memory before handoff.
Summarize blockers, risks, and go/no-go decision.

Release Checklist

Tests or manual verification completed.
Build/package succeeds.
No secrets in code, bundles, logs, or artifacts.
Migrations are reversible or risk-documented.
Feature flags or rollout plan exist when risk is high.
Release notes reflect actual changes.
Rollback path is known.
Monitoring/logging can identify failure.
.ai_project.md Docs Index and relevant docs/ files match the shipped behavior.

Desktop App Checks

Installer or bundle starts cleanly.
Auto-update metadata is correct when used.
Signing/notarization requirements are known.
OS permissions and native capabilities are documented.

Web/API Checks

Env vars are documented.
API compatibility and status codes are stable.
Cache and CDN behavior are considered.
Error monitoring is ready.

Output

发布判断：Go | No-Go | Conditional Go

已验证：
- ...

风险：
- ...

回滚：
- ...

项目记忆：
- ...

Boundaries

Do not claim files, generated media, deployments, scans, account changes, or external writes unless the active tool or command output proves them.
Do not override system, developer, user, project, or selected-skill rules.
If another skill is more specific for the user's intent, hand off or use it as the main skill instead of duplicating its workflow.

同仓库更多 Skills

同仓库

router

PAISHU-AI/PAI-zong-NB-v5.8

Route user requests to the right Codex role, output mode, and minimal skill set. Use for every task before deciding whether the answer is simple consultation, architecture, project assistance, coding, debugging, review, documentation, or rule maintenance.

2026-07-180

project-context

PAISHU-AI/PAI-zong-NB-v5.8

Inspect and summarize project context before coding. Use when Codex needs to modify a repository, understand structure, follow existing conventions, locate scripts, read AGENTS.md, README, package manifests, or project documentation.

2026-07-180

ui-design

PAISHU-AI/PAI-zong-NB-v5.8

Design practical user interfaces, flows, information architecture, layout systems, component states, and design tokens. Use for page design, UX redesign, dashboards, tools, mobile/web UI, interaction design, and before frontend implementation when visual or workflow decisions matter.

2026-07-180

frontend

PAISHU-AI/PAI-zong-NB-v5.8

Build and modify frontend pages, components, state logic, styling, forms, client-side interactions, and UI behavior in React, Vue, Svelte, vanilla HTML/CSS/JS, or similar frameworks. Use for frontend implementation and frontend bug fixes.

2026-07-180

backend

PAISHU-AI/PAI-zong-NB-v5.8

Implement backend services, business logic, API handlers, jobs, integrations, file processing, authentication flows, and server-side fixes. Use for backend coding and debugging in Node, Python, Go, Java, Rust, PHP, or similar stacks.

2026-07-180

api-design

PAISHU-AI/PAI-zong-NB-v5.8

Design REST, GraphQL, RPC, webhook, and internal service APIs. Use for routes, status codes, request/response schemas, error models, pagination, filtering, versioning, idempotency, and OpenAPI or contract documentation.

2026-07-180

name	ship-pro
description	Shipping and release readiness workflow for software changes. Inspired by gstack ship workflows and adapted for Codex v4.3. Use when preparing a feature, desktop app, web app, API change, or release for delivery, including final checks, docs, changelog, versioning, rollback, and deployment readiness.

Ship Pro

Workflow

Confirm scope: what is shipping and what is not.
Verify code quality: tests, lint, typecheck, build, and relevant manual checks.
Verify docs: .ai_project.md, feature docs, API docs, deployment notes, changelog.
Verify release safety: migrations, env vars, flags, rollback, monitoring, user impact.
Use production-readiness-pro for commercial go/no-go decisions.
Use project-sync-audit to catch stale project memory before handoff.
Summarize blockers, risks, and go/no-go decision.

Release Checklist

Tests or manual verification completed.
Build/package succeeds.
No secrets in code, bundles, logs, or artifacts.
Migrations are reversible or risk-documented.
Feature flags or rollout plan exist when risk is high.
Release notes reflect actual changes.
Rollback path is known.
Monitoring/logging can identify failure.
.ai_project.md Docs Index and relevant docs/ files match the shipped behavior.

Desktop App Checks

Installer or bundle starts cleanly.
Auto-update metadata is correct when used.
Signing/notarization requirements are known.
OS permissions and native capabilities are documented.

Web/API Checks

Env vars are documented.
API compatibility and status codes are stable.
Cache and CDN behavior are considered.
Error monitoring is ready.

Output

发布判断：Go | No-Go | Conditional Go

已验证：
- ...

风险：
- ...

回滚：
- ...

项目记忆：
- ...

Boundaries

Do not claim files, generated media, deployments, scans, account changes, or external writes unless the active tool or command output proves them.
Do not override system, developer, user, project, or selected-skill rules.
If another skill is more specific for the user's intent, hand off or use it as the main skill instead of duplicating its workflow.