Run any Skill in Manus with one click

sea-release

Stars1

Forks0

UpdatedMay 13, 2026 at 18:15

Canonical SEA-Forge release workflow for release preparation, validation, branch promotion, tagging, rollback, and release-gate evidence. Use when preparing a release, promoting dev to stage or stage to main, cutting a version tag, validating release readiness, handling hotfix forward-merges, planning rollback, or executing a full end-to-end release. Prefer existing just recipes and evidence-producing gates over ad hoc deployment steps.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

GodSpeedAI

GodSpeedAI/SEA

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

File Explorer

2 files

SKILL.md

readonly

name	sea-release
description	Canonical SEA-Forge release workflow for release preparation, validation, branch promotion, tagging, rollback, and release-gate evidence. Use when preparing a release, promoting dev to stage or stage to main, cutting a version tag, validating release readiness, handling hotfix forward-merges, planning rollback, or executing a full end-to-end release. Prefer existing just recipes and evidence-producing gates over ad hoc deployment steps.
disable-model-invocation	true

SEA Release

Run the repository's canonical release flow using existing just recipes, release gates, and evidence artifacts.

When To Use

Use when the user asks to:

prepare a release
validate release readiness
promote dev to stage
promote stage to main
cut a release tag
handle a hotfix release and forward-merge it back
plan rollback
run the full release end to end

Do not invent Docker, Kubernetes, registry, or package-publish steps.

Modes

Default mode: run checks autonomously, but stop before irreversible or production-sensitive actions.
e2e mode: if the release request includes the exact keyword e2e, treat that as one-time approval for the canonical end-to-end release flow, including promotions and tagging.
Inferred autonomy: if the request implies a full autonomous release but does not include e2e, ask for confirmation by telling the user to reply with e2e.

Core Rules

Prefer just recipes and existing repo scripts.
Treat just ci as the CI-parity check.
Treat just enterprise-governance-gate as the release-gate entrypoint.
Use promotion recipes instead of manual merges when a recipe exists.
Do not claim release-gate-proof or enterprise-shippable without executed validation and an evidence artifact.

Load Only What You Need

references/workflow.md: scope selection, e2e trigger behavior, preflight checks, promotion order, tag flow, rollback posture, and output shape.

Quick Reference

just ci-quick
just ci
just enterprise-governance-gate
just promote-stage
just promote-main
just release <version>
just hotfix-forward

Stop And Ask

Stop if the task would require:

destructive recovery or rollback
deleting or rewriting tags
acting on ambiguous branch, version, or release scope
claiming release readiness without executed proof

If autonomy is implied but e2e is absent, ask the user to confirm by replying with e2e.

More from this repository

same repository

skill-creator

GodSpeedAI/SEA

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends AI agent capabilities with specialized knowledge, workflows, or tool integrations.

2026-05-211

ai-harness-bootstrap

GodSpeedAI/SEA

Use when creating, scaffolding, or updating the repository AI harness in VS Code. Trigger on requests to bootstrap or refresh instructions, prompts, agents, hooks, skills, or memory layers while preserving useful existing structure and avoiding monolithic always-on context.

2026-05-131

sea-generator-first

GodSpeedAI/SEA

Use when SEA work touches specs, generators, manifests, semantic fixtures, regeneration, `src/gen`, or behavior projected from ADR/PRD/SDS/SEA authority.

2026-05-111

sea-last-mile

GodSpeedAI/SEA

Use when a SEA context has valid specs and generated contracts but lacks handwritten logic, runtime wiring, persistence, integration, tests, or executable proof.

2026-05-111

s1-context-bridge

GodSpeedAI/SEA

Create concise, copy-paste-ready bridge prompts between a repo-aware coding agent and an external strategic reasoning agent such as S1 ArchDevAgent. Use when the user wants to offload architecture, research, large refactor planning, migration design, plan critique, implementation-spec drafting, test-strategy design, whole-repo analysis, or diff review to an external agent while keeping repo inspection and implementation in the coding agent. Also use when the user says "use S1", "ask S1", "make a prompt for S1", "bridge this to my external agent", "prepare a context packet", or "validate this S1 response".

2026-05-101

case-management

GodSpeedAI/SEA

Manage knowledge work using CMMN (Case Management Model and Notation) primitives including Cases, Stages, Tasks, Sentries, and Milestones. Use for discretionary workflows, research projects, consulting engagements, creative work, or any knowledge-intensive work requiring flexible orchestration. Integrates with pm-orchestration for AI-driven case lifecycle management.

2026-04-181

name	sea-release
description	Canonical SEA-Forge release workflow for release preparation, validation, branch promotion, tagging, rollback, and release-gate evidence. Use when preparing a release, promoting dev to stage or stage to main, cutting a version tag, validating release readiness, handling hotfix forward-merges, planning rollback, or executing a full end-to-end release. Prefer existing just recipes and evidence-producing gates over ad hoc deployment steps.
disable-model-invocation	true

SEA Release

Run the repository's canonical release flow using existing just recipes, release gates, and evidence artifacts.

When To Use

Use when the user asks to:

prepare a release
validate release readiness
promote dev to stage
promote stage to main
cut a release tag
handle a hotfix release and forward-merge it back
plan rollback
run the full release end to end

Do not invent Docker, Kubernetes, registry, or package-publish steps.

Modes

Default mode: run checks autonomously, but stop before irreversible or production-sensitive actions.
e2e mode: if the release request includes the exact keyword e2e, treat that as one-time approval for the canonical end-to-end release flow, including promotions and tagging.
Inferred autonomy: if the request implies a full autonomous release but does not include e2e, ask for confirmation by telling the user to reply with e2e.

Core Rules

Prefer just recipes and existing repo scripts.
Treat just ci as the CI-parity check.
Treat just enterprise-governance-gate as the release-gate entrypoint.
Use promotion recipes instead of manual merges when a recipe exists.
Do not claim release-gate-proof or enterprise-shippable without executed validation and an evidence artifact.

Load Only What You Need

references/workflow.md: scope selection, e2e trigger behavior, preflight checks, promotion order, tag flow, rollback posture, and output shape.

Quick Reference

just ci-quick
just ci
just enterprise-governance-gate
just promote-stage
just promote-main
just release <version>
just hotfix-forward

Stop And Ask

Stop if the task would require:

destructive recovery or rollback
deleting or rewriting tags
acting on ambiguous branch, version, or release scope
claiming release readiness without executed proof

If autonomy is implied but e2e is absent, ask the user to confirm by replying with e2e.