Files
VincentShipsIt e20ffde84f Prune no-op text from skills, commands, and prompts
Remove text that doesn't change agent behavior (Matt Pocock's no-op test):
role-priming openers that restate the frontmatter description, "When to Use
This Skill" -> "When to Use", "Activate this skill when:" preambles, trailing
Skill Metadata provenance blocks, marketing adjectives
(comprehensive/world-class/robust), and justification clauses that state no
action. Dispatcher commands lose "instead of remembering which skill fits"
and "thin dispatcher" filler tails.

Frontmatter (name/description/license/etc.) left byte-for-byte untouched to
preserve discoverability. 155 SKILL.md + 11 commands + 1 prompt edited;
~247 net source lines removed. markdownlint passes; skill-sync validation
clean; marketplace bundles regenerated.
2026-06-29 15:02:50 +02:00

2.4 KiB

Deploy - Single Front Door for Deployment and Infra Provisioning

Drive the full deployment and infra lifecycle from one command — ship an app to staging or production, compose a repo-aware deployment workflow, wire an EC2 CI/CD pipeline, configure production monitoring, or scaffold a dev container.

Usage

/deploy                  # status: domain overview + usage
/deploy app              # deploy web app to staging or production
/deploy compose          # compose the smallest safe deploy workflow from repo signals
/deploy ec2              # wire Docker + GitHub Actions CI/CD pipeline to EC2
/deploy monitor          # set up Sentry error tracking and Google Analytics
/deploy devcontainer     # scaffold a VS Code Dev Container with Docker

Steps

  • app — the deploy skill: run deployment workflows for React, Next.js, or NestJS applications to preview, staging, or production, including pre-deploy gates, verification, and rollback guidance.
  • compose — the deployment-composer skill: inspect the repository's actual branching model, CI setup, and deploy provider, then compose the smallest safe deployment workflow, routing to focused sub-skills for quality gates, provider deployment, post-deploy verification, and rollback.
  • ec2 — the ec2-backend-deployer skill: set up a Docker-based CI/CD pipeline for NestJS, Next.js, or Express backends on EC2, using GitHub Actions and Tailscale for secure SSH access.
  • monitor — the monitoring-setup skill: configure Sentry error tracking and Google Analytics for NestJS and Next.js applications.
  • devcontainer — the devcontainer-setup skill: scaffold a complete VS Code Dev Container configuration with Docker, docker-compose, and optional Claude Code CLI support.

Workflow

Use the deploy-dispatch skill. It parses the subcommand and delegates to the right engine. Read-only until the delegated skill's own confirmation gate; it never mutates anything directly.

  1. Parse the argument into a mode (status / app / compose / ec2 / monitor / devcontainer). Unknown argument → print Usage, don't guess.
  2. Route to the delegated skill (or, for status, print a domain overview and the Usage block, then stop).
  3. Defer all preconditions and confirmation to the delegated skill — this command does not relax them.
  4. Never auto-chain subcommands — each action is its own invocation.