pre-deploy

Validate TypeScript projects with type-checking, linting, build, and security checks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/120ventures/claude-skills --skill pre-deploy-120ventures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-deploy
Source: https://github.com/120ventures/claude-skills/tree/main/pre-deploy
Command: npx skills add https://github.com/120ventures/claude-skills --skill pre-deploy-120ventures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This step helps teams catch type errors, lint issues, security gaps, and misconfigurations before deploying to production, reducing outages and rollback risk.

Core Features & Use Cases

  • TypeScript type-checking with npx tsc --noEmit
  • Linting with npm run lint
  • Build verification with npm run build
  • Environment variable checks by reading .env.example and ensuring .env is ignored
  • Security quick-scan to flag console logs and secrets
  • RLS checks to verify access controls in deployment environments

Quick Start

Run the pre-deploy checks in your CI or local environment to validate type-safety, linting, build, env vars, and RLS before deployment

Frequently Asked Questions about pre-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run pre-deployment checks for TypeScript and Node.js to catch type errors?

Pre-deployment validation for TypeScript and Node.js runs type-checking using 'npx tsc --noEmit' alongside linting and build verification. This ensures type errors, lint violations, and build failures are caught locally or in CI before release.

What is the best way to validate environment variables and prevent secrets exposure before deploying?

Validating environment variables involves reading '.env.example' to ensure required variables exist and confirming '.env' is ignored. A security quick-scan further flags exposed secrets and console logs to prevent leaks during deployment.

How do I verify Row Level Security checks in my CI/CD workflow before release?

Row Level Security (RLS) checks are verified during pre-deployment validation to confirm access controls are properly configured in deployment environments. This runs as part of comprehensive CI/CD checks before release.

Does this pre-deploy validation require any specific dependencies or components?

No specific dependencies are required. Pre-deploy validation ensures reproducible checks via standard npm scripts, relying only on your existing TypeScript, Node.js, and linting configurations to execute type, build, and security checks.

Why should I run pre-deployment security scans and what issues do they catch?

Pre-deployment security scans catch misconfigurations, exposed secrets, and console logs before they reach production. Running these scans reduces outages and rollback risk by identifying security gaps early in the CI/CD workflow.

Can I use npm scripts to run reproducible type-safety and build checks locally?

Yes, pre-deploy validation uses standard npm scripts to run reproducible type-safety, linting, and build checks. You can execute these locally or integrate them directly into your CI/CD pipeline to ensure consistent results.