deploy

Enforce preflight checks and rollback readiness for CI/CD deployments.

4|2|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/finger-gun/sisu --skill deploy-finger-gun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/finger-gun/sisu/tree/main/packages/skills/skill-deploy
Command: npx skills add https://github.com/finger-gun/sisu --skill deploy-finger-gun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deployment processes are error-prone and hard to roll back; this skill provides checklist-driven safety practices to ensure reliable releases.

Core Features & Use Cases

  • Checklist-driven safety checks to verify tests, environment variables, builds, and migrations before deployment.
  • Rollback readiness with explicit rollback steps, health checks, and post-deploy validation.
  • Audit-friendly deployment logs and metrics to support post-mortem analysis.
  • Use Case: In a multi-service release, safely deploy and rollback if health checks fail.

Quick Start

Run the deployment skill to validate and execute a release with rollback safeguards.

Frequently Asked Questions about deploy

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

FAQPage Schema
How do I automate safe deployments with rollback readiness?

Automate safe deployments by enforcing a preflight checklist for builds, tests, and migrations, and defining explicit rollback procedures. This ensures repeatable releases across services and infrastructure with health checks and post-deploy validation.

What is a checklist-driven deployment process?

A checklist-driven deployment verifies tests, environment variables, builds, and database migrations before releasing. It enforces safety checks to prevent errors and ensures rollback readiness with explicit steps and post-deploy health validation.

How do I handle rollback if health checks fail after a release?

Handle rollback failures by defining explicit rollback procedures and post-deploy health checks. If validation fails, the deployment process executes the rollback steps to safely revert services, databases, or infrastructure to their previous state.

Does this deployment approach work for manual releases and CI/CD pipelines?

Yes, this deployment approach applies to both CI/CD pipelines and manual releases. It automates builds, health checks, and post-deploy validation across services, databases, and infrastructure while maintaining audit-ready logs.

What's the best way to maintain audit-friendly logs for software deployments?

Maintain audit-friendly deployment logs by capturing metrics and validation results during the release process. Checklist-driven deployments generate audit-ready records that support post-mortem analysis for multi-service releases.

When should I not use automated checklist deployments?

Avoid automated checklist deployments when your release lacks defined health checks or explicit rollback procedures. Without post-deploy validation and rollback readiness for services, databases, and infrastructure, the safety checks cannot reliably execute.