deploy

Automate end-to-end deployment workflows with tests, syncs, restarts, and staged rollouts.

12|2|Updated Feb 2, 2020
One-click install
npx skills add https://github.com/servitola/dotfiles --skill deploy-servitola
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/servitola/dotfiles/tree/main/claude-code/skills/deploy
Command: npx skills add https://github.com/servitola/dotfiles --skill deploy-servitola

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploy workflows are error-prone and slow; this skill automates end-to-end deployment tasks, reducing risk and manual toil.

Core Features & Use Cases

  • Standard deploy flow: run tests, sync changed files to server, restart services, verify, and commit.
  • Staged rollout: enable features behind flags with canary and gradual rollout.
  • Rollback readiness: provides a rollback plan template and trigger conditions for safe rollback.

Quick Start

Run the standard deploy flow on your changed project and apply staged rollout when introducing user-visible changes.

Frequently Asked Questions about deploy

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

FAQPage Schema
How do I automate an end-to-end deployment workflow to reduce manual toil?

You can coordinate staged rollouts for user-visible changes by enabling features behind feature flags, applying canary-style deployment thresholds, and monitoring health verification before full rollout.

What is a canary-style rollout and how does it work with feature flags?

A canary-style rollout gradually enables features behind flags for a subset of users, applies rollout thresholds, and verifies service health before proceeding to full deployment to minimize risk.

How do I plan a rollback for a failed staged rollout?

Planning a rollback for a failed staged rollout involves using a rollback plan template, defining trigger conditions for safe rollback, and executing the rollback when health verification fails.

Does this deployment automation work for server management without external CI/CD dependencies?

This deployment automation works for server management without external dependencies, synchronizing changed files to servers, restarting services, and verifying health independently of external CI/CD pipelines.

What's the best way to verify service health after restarting services during a deployment?

The best way to verify service health after restarting services during a deployment is to run automated health checks as part of the standard deploy flow before committing changes and completing the rollout.