ワンクリックでManusで任意のスキルを実行

ship

スター5

フォーク4

更新日2026年7月23日 09:27

Prepare deploy, pull request, or release readiness. Use when packaging completed work for review, release, deployment, handoff, final quality gates, TDD evidence review, security checks, or PR preparation.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

produtoreativo

produtoreativo/payments-api

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

SHIP

Use this skill to prepare completed work for delivery.

For detailed Codex submission mechanics, read references/workflow.md.

Inputs

AGENTS.md
prodops/artifacts/plans/reliability/
prodops/artifacts/trails/sessions/ (active session trail)
prodops/framework/journeys/delivery/phases/finish/quality-gates.md
Current branch diff and validation evidence

Flow

Confirm the change maps to the current Reliability Plan or documented follow-up.
Confirm the branch and diff against the intended base.
Verify TDD evidence for behavior changes.
Run final quality gates: format, lint, build and tests appropriate to the changed files.
Run security checks for secrets, unsafe config, dependency changes and accidental environment leakage.
Review the diff as if doing code review.
Summarize changed behavior, impacted artifacts and deployment risk.
Identify rollback, monitoring and operational notes when applicable.
Prepare PR or deploy notes.
Append shipping evidence to the Release Trail.

Guardrails

Do not ship undocumented behavior changes.
Do not present missing evidence as complete.
Do not change business scope during ship preparation.
Do not include unrelated changes in the PR or deployment package.
Do not commit secrets, real tokens, personal credentials or local-only paths.
Tests must cover changed behavior or the residual test gap must be explicit.
Behavior changes must show TDD evidence or explain why TDD was not applicable.
PR or deploy notes must explain behavior, validation and risk.

Engineering References

Reference	When to read
`../references/engineering/tdd-prodops/workflow.md`	TDD evidence standards (what counts as red/green/refactor proof)
`../references/engineering/tdd-prodops/quality-gates.md`	Delivery gates checklist before creating a PR

このリポジトリの他の Skills

同じリポジトリ

diligence-diligence-async

produtoreativo/payments-api

Proactive drift-scan cycle. Reads all active OBCs and Issues, identifies divergences, and repairs what can be automated. Runs across the entire active backlog, not for a specific OBC.

2026-07-245

diligence-scan

produtoreativo/payments-api

Read all active OBCs and compare declared state with backlogs and external tools. Produces a divergence list. Does not repair — only identifies gaps.

2026-07-245

diligence-diligence-sync

produtoreativo/payments-api

Event-driven cycle triggered by a product decision. Captures the decision as an OBC, attaches a Work Item, promotes it through the backlog hierarchy, and closes it when the OBC reaches Operational. Runs for a specific OBC.

2026-07-245

diligence-capture

produtoreativo/payments-api

Create or update an OBC from the decision that triggered the Diligence Sync cycle. Use when an Assessment decision, Discovery experiment, or Operation signal requires canonical state to be recorded before Work Items are created.

2026-07-245

diligence

produtoreativo/payments-api

Synchronize OBC state across backlogs and tools. Runs event-driven cycle (diligence-sync) or proactive drift-scan cycle (diligence-async). Never touches product code.

2026-07-245

diligence-flag

produtoreativo/payments-api

Classify divergences from Scan and register them as pending Diligence items with severity and corrective action. Does not repair — only signals.

2026-07-235

SHIP

Use this skill to prepare completed work for delivery.

For detailed Codex submission mechanics, read references/workflow.md.

Inputs

AGENTS.md

prodops/artifacts/plans/reliability/

prodops/artifacts/trails/sessions/ (active session trail)

prodops/framework/journeys/delivery/phases/finish/quality-gates.md

Current branch diff and validation evidence

Flow

Confirm the change maps to the current Reliability Plan or documented follow-up.

Confirm the branch and diff against the intended base.

Verify TDD evidence for behavior changes.

Run final quality gates: format, lint, build and tests appropriate to the changed files.

Run security checks for secrets, unsafe config, dependency changes and accidental environment leakage.

Review the diff as if doing code review.

Summarize changed behavior, impacted artifacts and deployment risk.

Identify rollback, monitoring and operational notes when applicable.

Prepare PR or deploy notes.

Append shipping evidence to the Release Trail.

Guardrails

Do not ship undocumented behavior changes.

Do not present missing evidence as complete.

Do not change business scope during ship preparation.

Do not include unrelated changes in the PR or deployment package.

Do not commit secrets, real tokens, personal credentials or local-only paths.

Tests must cover changed behavior or the residual test gap must be explicit.

Behavior changes must show TDD evidence or explain why TDD was not applicable.

PR or deploy notes must explain behavior, validation and risk.

Engineering References

Reference

When to read

../references/engineering/tdd-prodops/workflow.md

TDD evidence standards (what counts as red/green/refactor proof)

../references/engineering/tdd-prodops/quality-gates.md

Delivery gates checklist before creating a PR

name	ship
description	Prepare deploy, pull request, or release readiness. Use when packaging completed work for review, release, deployment, handoff, final quality gates, TDD evidence review, security checks, or PR preparation.