Skip to content

pantyuhov9-web/agentic-workflow-template / .claude/skills/deploy

deploy

Verified

Deploy a site — local preview, pre-flight checks, or production push. Defaults to Hostinger git auto-deploy (push to main triggers Hostinger pull) with FTP fallback for non-Hostinger sites.

FileKindSize
SKILL.mdskill md1.6 KB
---
name: deploy
description: Deploy a site — local preview, pre-flight checks, or production push. Defaults to Hostinger git auto-deploy (push to main triggers Hostinger pull) with FTP fallback for non-Hostinger sites.
allowed-tools:
  - Bash
  - Read
  - Edit
  - Write
  - Glob
  - Grep
  - TodoWrite
model: sonnet
argument-hint: <"preview" | "check" | "push" | "setup-ci">
---

# Deploy — site deployment lifecycle (entry point)

This skill is the invocation handle for the deploy lifecycle. The full procedure — per-site deploy mechanism, pre-flight, approval gate, FTP fallback, CI setup, and the Cloud-Function redeploy note — is the **single source of truth** in the workflow. This file just routes you there.

## Sub-commands

- `deploy preview` — local preview server
- `deploy check` — pre-flight checks before pushing
- `deploy push` — production deploy (approval-gated)
- `deploy setup-ci` — generate GitHub Actions config (non-Hostinger sites)

## Begin

Read [workflows/site_deploy.md](../../../workflows/site_deploy.md) — authoritative SOP — and execute the section matching `$ARGUMENTS`. Defaults: site root = `--root` or cwd (`~/Sites/<name>/` convention); for sites on a git-auto-deploy host (e.g. Hostinger auto-pull, ~1–2 min), `git push origin main` IS the deploy.

**Non-negotiable** (also in the workflow): approval gate before every push (show diff + detected method) · pass pre-flight first · never force-push · git status clean.

## See also

- [tools/deploy_site.py](../../../tools/deploy_site.py) — FTP/SFTP/rsync deployer (fallback)
- [tools/site_audit.py](../../../tools/site_audit.py) — pre-flight checks
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall