agentleFS
GlamgarOnDiscordGlamgarOnDiscord/claude-saas-blueprint/.claude/skills/deploy-check/SKILL.md

deploy-check

Skill2 starsChanged 6 months agoMITView on GitHub

Validation complète pré-déploiement. Supporte Vercel, Railway, Docker/VPS. Utilise les scripts Python du projet.

  • Reads credentials

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Arguments

  • env : staging | production

Étape 1 — Pre-deploy checks (script unifié)

python scripts/pre_deploy_check.py --env [staging|production]

Couvre : TypeScript, lint, tests, secrets, .env.example, console.log, migrations, RLS. Bloquer si exit 1.

Étape 2 — Plateforme de déploiement

Vercel (recommandé SaaS Next.js)

vercel --env staging      # Preview URL
vercel --prod             # Production

Variables requises dans Vercel : DATABASE_URL (pooler port 6543), DIRECT_URL (port 5432), NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY.

Railway

railway up --environment staging
railway up --environment production

Docker / VPS (Coolify, Dokku)

docker build -t app:$(git rev-parse --short HEAD) .
docker push [registry]/app:[tag]
# Puis trigger deploy via webhook ou CLI Coolify/Dokku

Étape 3 — Migrations DB (si Supabase)

python scripts/supabase_migrate.py --diff          # Voir ce qui va être appliqué
python scripts/supabase_migrate.py --env [env]     # Appliquer
python scripts/supabase_rls_check.py               # Vérifier RLS

Étape 4 — Post-deploy

  1. Smoke test : curl https://[domain]/api/health
  2. Logs plateforme — 0 erreur 500 dans les 2 premières minutes
  3. Sentry — nouvelles erreurs ?
  4. Mettre à jour .claude/memory/session.md avec la version déployée

Rollback

Vercel : vercel rollback [deployment-url] Railway : railway rollback Docker : redéployer le tag précédent DB : créer une nouvelle migration inverse (python scripts/supabase_migrate.py --new rollback-[feature])

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.