Production Deployment Phase FAQs

Question 1

Does this skill support semantic versioning?

Accepted Answer

Yes, it determines the appropriate version bump (Major, Minor, or Patch) based on changes and updates files like package.json and CHANGELOG.md automatically.

Question 2

How does the skill ensure a deployment is safe?

Accepted Answer

It verifies that staging validation is approved in the state.yaml file, confirms rollback procedures are tested, and runs a battery of health checks against the production environment after deployment.

Question 3

What is included in the Ship Report?

Accepted Answer

The ship report includes the version number, deployment timestamp, deployment ID, health check results, git SHAs, and a specific rollback procedure for that release.

Question 4

What is the primary purpose of the production-deployment-phase skill?

Accepted Answer

It automates the final stage of the development lifecycle, promoting code from staging to production while ensuring all quality gates, health checks, and versioning requirements are met.

Question 5

What deployment platforms are compatible?

Accepted Answer

The skill is flexible and supports various deployment models including direct git pushes to production branches, GitHub Actions workflows, and platforms like Vercel or Netlify.

Production Deployment Phase

Key Features

Use Cases

Production Deployment Phase

Key Features

Use Cases