Deploy

Name: Deploy
Author: antoine-tena

ASecurity

Deploy the project to production with the repo's scripts (scripts/ops/), after checking that CI on the integration branch is green.

2 stars
0 votes
0 copies
0 views
Added October 21, 2026

developmentgitapidatabasefrontendbackend

Works with

Security analysis

A100/100

Scanned October 21, 2026

npx -y skills add antoine-tena/kiln --skill deploy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Deploy?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/antoine-tena-deploy/badge)](https://www.skillsdirectory.com/skills/antoine-tena-deploy)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: deploy
description: Deploy the project to production with the repo's scripts (scripts/ops/), after checking that CI on the integration branch is green.
disable-model-invocation: true
argument-hint: "[back|front|all] [rebuild]"
---

Requested deployment: `$ARGUMENTS` (default: backend, then frontend).
Repo settings: !`env | grep -E '^(KILN|PROJET)_(PROJECT|NOM|VPS|SITE|API_HEALTH|API_SANTE|PROD_DOC|DOC_PROD)' | sort`
(Repos generated before kiln 0.4 use the French names: `PROJET_NOM`, `PROJET_VPS`,
`PROJET_API_SANTE`, `PROJET_DOC_PROD`.)
Available scripts: !`ls scripts/ops/ 2>/dev/null | tr '\n' ' '`

**Project specifics** (options, pitfalls, extra steps): the "Specifics" section of the
production document (`$KILN_PROD_DOC`, by default `docs/operations/production.md`), to read in
full before starting; it takes precedence over what follows.

1. The integration branch is pushed and CI on its last commit is green: verdict of `kiln ci`
   (`kiln ci --status <integration>`, for a repo whose GitHub CI does not run) or GitHub CI
   (`gh run list -b <integration> -L 3`). Never run: start `kiln ci <integration>` (about twenty
   minutes) and wait for its verdict. Red: show the failing job and stop.
2. **Backend**: `scripts/ops/deploy-backend.sh`. Deployments **migrate** and keep the data; a
   database rebuild only if the `rebuild` argument is given. Then `scripts/ops/smoke-test.sh`
   (or `smoke.sh`) if it exists.
3. **Frontend**: `scripts/ops/deploy-frontend.sh`, with no untracked file in the frontend directory.
4. Summarize: deployed commit, result of the health probe
   (`curl -s -o /dev/null -w '%{http_code}' $KILN_API_HEALTH`) and of the smoke test. If
   something is wrong: skill `/vps:prod-logs`.