skills.rest
EndUser123
EndUser123COMMUNITY
Explore all skills by this author →
GitHub

ship

Aggregate git, verification, QA, CI/CD, and runtime signals into a ship readiness verdict.

Updated Apr 23, 2026
Search Tags:#deployment#qa#verification#ci-cd#ship#readiness#runtime-health
One-click install
npx skills add https://github.com/EndUser123/cc-skills-utils --skill ship-enduser123
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/EndUser123/cc-skills-utils/tree/main/skills/ship
Command: npx skills add https://github.com/EndUser123/cc-skills-utils --skill ship-enduser123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aggregate git, verification, QA, CI/CD, and basic runtime signals into a single "ship readiness" verdict.

Core Features & Use Cases

  • Mode detection: infer pre-deploy, post-deploy, or status from user input and context.
  • Pre-deploy flow: run /vdate-deploy to verify git cleanliness and branch, run /verify with at least T1/T2, optionally /qa, and query CI/CD for latest pipeline status.
  • Post-deploy flow: identify last deployment for the current branch/service, compare pre/post metrics, and flag regressions or anomalies.
  • Status flow: provide a combined summary of current state; no hard go/no-go verdict—informational.
  • Output: deliver a concise ship report with mode, statuses, final verdict (Ready/Caution/Blocked), and recommended next actions.

Quick Start

Run a ship pre-check on the current branch to verify readiness.

Frequently Asked Questions about ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check deployment readiness across git, CI/CD, and QA?▼

Deployment readiness is determined by aggregating git status, verification depth, QA scope, and CI/CD pipeline results into a single Ready, Caution, or Blocked verdict with a concise rationale.

What is the best way to validate post-deployment health and detect regressions?▼

Post-deployment health validation works by identifying the last deployment for a branch, comparing pre and post metrics, and flagging runtime anomalies or regressions in the combined ship report.

Can I get a status snapshot of my environments without a hard go or no-go verdict?▼

Status snapshots provide an informational summary of the current state across branches and environments, intentionally omitting a hard go or no-go verdict to serve as a combined informational overview.

How do I run a pre-deploy verification flow for my current branch?▼

Pre-deploy verification runs by checking git cleanliness and branch status, executing verification tiers T1 and T2, optionally running QA, and querying the latest CI/CD pipeline status before rendering a verdict.

How does the ship readiness verdict coordinate runtime health signals with QA scope?▼

The ship readiness verdict coordinates mode detection, verification depth, QA scope, and basic runtime health signals to produce a concise final verdict with recommended next actions.

Do I need external dependencies to aggregate CI/CD and QA signals for a ship readiness report?▼

Aggregating CI/CD, QA, git, and runtime signals into a ship readiness report requires no external dependencies, relying entirely on internal mode detection and signal coordination logic.

Related Skills

Explore More Software Engineering Skills→
softsparksoftspark
161

deploy

Automates pre-flight checks and health verification for multi-environment deployment workflows.

Community
Advanced
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

staging-deployment-phase

Coordinate staging deployments with migrations, health checks, and verification.

Community
Intermediate
burgebjburgebj

health

Monitor code quality with type checkers, linters, and test runners.

Community
Intermediate
1479089714790897
7

kwp-engineering-deploy-checklist

Generate pre-deployment verification checklists with rollback triggers and CI/CD status checks.

Community
Intermediate