node-craft-ops
/node-craft-ops
Operations rules for a Node.js/TypeScript backend: deploying on any platform (PaaS, containers or VMs: build, start, a single release step for migrations, port and host binding, private networking, health checks, instances, draining and graceful shutdown, versioned service config), liveness and readiness endpoints, CI/CD quality gates from immutable install to staging smoke test, migration release and rollback strategy, PostgreSQL backup, restore tests, RPO and RTO, and runbooks for alerts, failed jobs, webhook replay and incidents. Use when setting up or changing deployment, CI, health checks
- Author
- hasaneks ↗
- Repository
- node-craft ↗
- Licence
- MIT
- Last repository change
- 04.11.2026
Assessment and security
- Files in this package
- 6
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 04.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Operations rules for a Node.js/TypeScript backend: deploying on any platform (PaaS, containers or VMs: build, start, a single release step for migrations, port and host binding, private networking, health checks, instances, draining and graceful shutdown, versioned service config), liveness and readiness endpoints, CI/CD quality gates from immutable install to staging smoke test, migration release and rollback strategy, PostgreSQL backup, restore tests, RPO and RTO, and runbooks for alerts, failed jobs, webhook replay and incidents. Use when setting up or changing deployment, CI, health checks
Original author description
Operations rules for a Node.js/TypeScript backend: deploying on any platform (PaaS, containers or VMs: build, start, a single release step for migrations, port and host binding, private networking, health checks, instances, draining and graceful shutdown, versioned service config), liveness and readiness endpoints, CI/CD quality gates from immutable install to staging smoke test, migration release and rollback strategy, PostgreSQL backup, restore tests, RPO and RTO, and runbooks for alerts, failed jobs, webhook replay and incidents. Use when setting up or changing deployment, CI, health checks
How it works
- Rules that apply everywhere
- Release checklist
SKILL.md preview
--- name: node-craft-ops description: "Operations rules for a Node.js/TypeScript backend: deploying on any platform (PaaS, containers or VMs: build, start, a single release step for migrations, port and host binding, private networking, health checks, instances, draining and graceful shutdown, versioned service config), liveness and readiness endpoints, CI/CD quality gates from immutable install to staging smoke test, migration release and rollback strategy, PostgreSQL backup, restore tests, RPO and RTO, and runbooks for alerts, failed jobs, webhook replay and incidents. Use when setting up or changing deployment, CI, health checks, shutdown, backups or runbooks, or preparing a release. Never starts paid resources or a production release on its own." --- # Ship and run the backend Follow `node-craft` for the working rules. Writing a deploy configuration is not a request to deploy: creating paid resources, changing production settings and releasing to production need explicit approval each time. | Area | Read | |---|---| | Choosing and recording the platform, build, start, release step, networking, instances, storage, config | `references/deployment.md` | | `/health/live`, `/health/ready`, signals, draining, crash handling | `references/health-shutdown.md` | | CI gates, release flow, migration and rollback order | `references/ci-gates.md` | | Backups, restore tests, RPO/RTO, data recovery | `references/backup-restore.md` | | Alerts, failed jobs, webhook replay, incident steps | `references/runbooks.md` | ## Rules that apply everywhere - **Same versions everywhere:** Node and Yarn from project metadata in local, CI and deploy builds. - **Build builds; it does not migrate.** Migrations run once per release in a single release step, with a lock; never at every replica start; never inside the image build. - **A failed migration stops the release.** No traffic goes to a version whose migration failed. - **Stateless processes.** Sessions, locks, rate limits and schedules that must be shared live in PostgreSQL or Redis, not in process memory. User files live in object storage. - **Health checks tell the truth.** Never make a health endpoint return success to get past a deploy. - **Shutdown is bounded.** Stop accepting work, finish in-flight work within the platform's draining time, close connections, exit. - **Recovery is tested.** A backup that was never restored is a hope. Record restore tests with dates and durations. - **No platform is assumed.** Use the project's platform, or record the choice in an ADR; map its pieces (release step, health checks, grace period, networking) in `STACK.md` (`references/deployment.md`). Platform features, limits, prices and config formats change; check the current docs before relying on them. ## Release checklist 1. CI green on the commit (`references/ci-gates.md`). 2. Migration reviewed for lock time and old-code compatibility; backup recent; data-loss risk approved if any. 3. Staging deploy: release-step migration succeeds, health checks pass, smoke tests pass, sandbox integrations checked. 4. Production release with approval; watch errors, latency, queue and outbox lag for the agreed period. 5. Rollback plan known: application rollback, and which applies to the database (old code compatible, forward fix, or restore). When a release or migration fails: stop, report the failure, its impact and the state it left openly, then choose forward fix or restore (`references/backup-restore.md`). Never hide it by faking health, skipping a gate or rerunning until it passes.
Files in this package (6)
- SKILL.md 3 KB
- references/backup-restore.md 2 KB
- references/ci-gates.md 3 KB
- references/deployment.md 6 KB
- references/health-shutdown.md 3 KB
- references/runbooks.md 2 KB
Versions
The database has no other skills named node-craft-ops.
Database snapshot: 13.11.2026 · package version 79975a7901f5 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100health-checks
Health check and graceful shutdown patterns. Liveness and readiness probes, dependency health checks, Kubernetes probes, Spring Actuator health, and zero-downtime shutdown. USE WHEN: user mentions "health check", "liveness", "readiness", "probe", "graceful shutdown", "SIGTERM",… - 100backup-drill
Prove backups restore. Inventories every data store, restores into a non-production target, verifies counts and an app smoke test, measures RPO and RTO, writes a runbook. Use when asked to test backups, restore drill, disaster recovery, can we recover the database, is our backup… - 100data-integrity
Protect data integrity and recoverability: RPO/RTO/RWO, backups vs snapshots, restore testing, and 'what you read is what you wrote'. Use for data risk reviews and backup strategy. - 100db-backup
Sets up automated database backup, restore, and disaster recovery procedures for PostgreSQL, MySQL, MongoDB, and Redis. Use when you need to implement backup schedules, point-in-time recovery, cross-region replication, backup verification, or disaster recovery runbooks. Trigger… - 90resiliency-recovery
Build or audit availability and recoverability for a Singapore government system against the ICT&SS Policy Reform (IM8 successor) Resiliency (RS-1..RS-3) and Backup & Recovery (BR-1..BR-6) controls: multi-AZ deployment with health checks and failover, load balancing and… - 100disaster-recovery
Backup and disaster-recovery standards — defining RTO/RPO, 3-2-1 and offsite copies, immutable backups (S3 Object Lock, Azure immutable blob storage, GCS retention), backup layers for Kubernetes objects, volumes and databases (GitOps, Velero, Longhorn, pgBackRest), restore…