deployment

Deploy built artifacts with pre-deployment gates, rollback plans, and post-deployment health checks.

130|8|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/sandgardenhq/sgai --skill deployment-sandgardenhq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment
Source: https://github.com/sandgardenhq/sgai/tree/main/cmd/sgai/skel/.sgai/skills/deployment
Command: npx skills add https://github.com/sandgardenhq/sgai --skill deployment-sandgardenhq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It ensures safe, reliable deployment of built artifacts by enforcing pre‑deployment checks, rollback planning, and post‑deployment verification, preventing accidental releases.

Core Features & Use Cases

  • Pre‑deployment gates: tests, build, lint, versioning, and configuration checks.
  • Artifact verification: existence, version, integrity, and size validation.
  • Environment validation: reachability, required services, configuration correctness, resource availability, and incident status checks.
  • Rollback plan enforcement: documented, tested procedures with trigger conditions and time estimates.
  • Controlled execution: reads .deploy/ instructions, logs deployment actions, and monitors for errors.
  • Post‑deployment verification: health checks, smoke tests, performance monitoring, and error rate analysis.

Use case: When a GOAL.md demands deploying an application to staging or production, this skill orchestrates the entire safe deployment flow.

Quick Start

Ask the assistant to run the deployment skill for your project, ensuring all safety gates are checked before releasing the artifact.

Frequently Asked Questions about deployment

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

FAQPage Schema
How do I enforce safety gates before deploying to staging or production?

Safe deployment requires executing pre-deployment gates including tests, build, lint, versioning, and configuration checks before releasing any artifact. This skill reads .deploy/ instructions to enforce those gates automatically, preventing accidental releases to staging or production environments.

What does artifact verification involve during a deployment?

Artifact verification validates existence, version, integrity, and size of built artifacts before they reach target environments. This ensures only correct, uncorrupted artifacts are deployed, catching build issues early in the deployment pipeline.

How do I set up rollback procedures for a production deployment?

Rollback planning requires documented, tested procedures with defined trigger conditions and time estimates specified in a .deploy/ directory. This skill enforces rollback plan presence before deployment begins, ensuring you can recover quickly if post-deployment health checks fail.

What environment validation checks are needed before deploying an application?

Environment validation checks target reachability, required services, configuration correctness, resource availability, and incident status before deployment proceeds. These checks confirm the target environment is healthy and ready to receive the artifact without causing downtime.

Do I need a .deploy/ directory to use automated deployment safety checks?

Yes, a .deploy/ directory is required to define commands, checks, and rollback procedures. The skill reads these instructions to orchestrate pre-deployment gates, artifact verification, environment validation, and post-deployment health checks as specified.

What post-deployment verification should I run after releasing an artifact?

Post-deployment verification includes health checks, smoke tests, performance monitoring, and error rate analysis after the artifact reaches the target environment. This skill monitors for errors and logs deployment actions, triggering rollback procedures if health checks fail.