ericrisco/rsc-harness / skills/deployment
deployment
VerifiedUse when taking an app from source to live: choosing the deploy target from requirements (Hetzner+Coolify vs Vercel vs a third), then wiring container → CI → registry → host with build secrets, healthchecks and rollback. NOT one platform's mechanics (that is `coolify`, `vercel`, `railway`, `render`), NOT the Dockerfile alone (that is `docker`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.4 KB |
| evals/README.md | markdown | 2.7 KB |
| evals/cases.yaml | config | 5.7 KB |
| references/coolify.md | markdown | 14.3 KB |
| references/dockerfiles-by-stack.md | markdown | 10.6 KB |
| references/github-actions.md | markdown | 8.9 KB |
| references/hosting-targets.md | markdown | 15.4 KB |
| scripts/verify.shexecutable | script | 6.3 KB |
evals/cases.yaml
View on GitHubskill: deployment
should_trigger:
- prompt: "Write a Dockerfile for my FastAPI service and a GitHub Actions workflow that lints, tests, scans the image, and pushes it to ghcr."
why: "Core scope: authoring a multi-stage Dockerfile plus a least-privilege GHA build/test/scan/push pipeline — exactly the source→container→CI→registry path this skill owns."
- prompt: "We're paying too much on Vercel for our Next.js app. Where should we move it to cut the bill while keeping deploys easy?"
why: "Hosting-decision question (Vercel vs Hetzner+Coolify vs a third option) is explicitly the 'where should I host this' / decision-matrix scope, including the start-on-Vercel-move-to-Coolify escape hatch."
- prompt: "How do I get a private npm token into my Docker build without it ending up in the image history?"
why: "Doesn't name the skill or 'Docker' as a topic per se, but this is the BuildKit --mount=type=secret vs ARG decision — a signature build-secrets concern of this skill."
- prompt: "Set up zero-downtime deploys for my service on our self-hosted PaaS, with a healthcheck that gates the swap and a way to roll back fast."
why: "Rolling/blue-green strategy, healthcheck-gated swap, and rollback path on Coolify-class hosting — squarely the deploy-target wiring this skill covers, even though 'Coolify' isn't named."
- prompt: "My GitHub Actions workflow uses permissions: write-all and stores a registry password as a secret. Can you harden it?"
why: "Least-privilege GITHUB_TOKEN (default-deny, per-job escalation) plus replacing a long-lived registry key with OIDC/GITHUB_TOKEN — both are explicit hardening targets of this skill."
- prompt: "Can you give me a compose file so I can run my app plus Postgres locally with hot reload?"
why: "docker-compose for local dev with a Postgres service, host-only port binding, and watch/hot-reload is an explicit 'When to use' item (compose.yaml authoring)."
- prompt: "Ship it — the app's ready, I just need it live somewhere with CI doing the build."
why: "'Ship it' is a named trigger phrase; the under-specified deploy + CI build intent is exactly what this skill operationalizes (and it will gather hosting requirements)."
should_not_trigger:
- prompt: "Write the SQLAlchemy migration to add a nullable email_verified column and backfill it."
route_to: "postgresdb"
why: "DB schema/migration logic is application/data-layer work; this skill explicitly defers runtime/migration logic to the per-stack/DB skills and stops at the container boundary."
- prompt: "Add a rate limiter and validate the JWT on my FastAPI auth endpoints before they hit the handler."
route_to: "security-audit"
why: "Input validation and authn/z hardening is security-audit's domain; this skill assumes the app already does this and does not author runtime auth code."
- prompt: "Convert my Docker Compose stack to a Kubernetes Helm chart with an HPA and an ingress."
route_to: "none"
why: "Kubernetes/Helm orchestration is explicitly out of scope ('say so and stop'); no sibling covers it, so it should not route into deployment."
- prompt: "Build my Next.js page that streams server components and add the data-fetching layer for the dashboard."
route_to: "nextjs"
why: "Application runtime code for the Next.js stack — the nextjs skill owns code that runs inside the container; deployment only containerizes/ships it."
- prompt: "Provision a Hetzner server, VPC, and firewall rules using Terraform."
route_to: "none"
why: "Cloud IaC (Terraform/Pulumi/CloudFormation) provisioning is explicitly out of scope; only the GHA↔cloud OIDC handshake is covered, not infrastructure provisioning."
capability:
- scenario: "Dockerize a FastAPI app and add a GitHub Actions pipeline that builds, tests, scans, and pushes to ghcr with no long-lived secrets."
must_include:
- "Multi-stage Dockerfile: full-toolchain builder stage + minimal runtime stage (distroless python3 or python:3.13-slim), never shipping the build toolchain"
- "Lockfile + manifest copied and deps installed BEFORE copying source, so source edits don't bust the dependency cache layer"
- "Runs as non-root (USER nonroot / UID 65532) and includes a HEALTHCHECK hitting a real readiness path like /readyz, not /"
- "A .dockerignore (excluding .git, .env*, __pycache__, etc.) written before the first build"
- "GHA workflow with top-level permissions: contents: read (default-deny) and per-job escalation (packages: write, id-token: write) only on build-push"
- "Pushes to ghcr.io using GITHUB_TOKEN/OIDC (no stored registry password) and runs a trivy image scan failing on HIGH/CRITICAL"
- "Third-party actions pinned to a commit SHA (not a moving tag) and a verify/lint+test gate before build"
- scenario: "User asks where to host a steady-traffic, EU-resident SaaS with its own Postgres and websockets, on a tight budget."
must_include:
- "Gathers requirements first: traffic shape (steady vs spiky), concurrent users, budget ceiling, data region/residency & compliance, ops comfort, stateful needs"
- "Recommends exactly THREE targets with trade-offs rather than a single host"
- "Names Hetzner VPS + Coolify as the fit for cost-sensitive / EU-resident / sustained / self-hosted-stateful workloads"
- "Names Vercel as the zero-ops serverless/edge option (best for Next.js + spiky, scale-to-zero) and notes its cost climbs at sustained scale / US-default region"
- "Offers a fitting third option (e.g. Railway for simple/predictable, Fly.io for global edge, or a hyperscaler for enterprise compliance)"
- "Notes the Dockerfile is the portability escape hatch — same artifact lets you move hosts later"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |