Pre-Deployment Security Check

Scan your code for hardcoded secrets before pushing by detecting API keys, passwords, and environment variables in JavaScript/TypeScript codebases. This Skill identifies exposed credentials in .env files, .gitignore configuration, and commit content, then generates a security report with remediation steps to block credential leakage.

Pre-deploy security checks detect hardcoded GEMINI_API_KEY, JWT_SECRET, DATABASE_PASSWORD, AZURE_AD_CLIENT_SECRET, and other sensitive patterns in your codebase. The scan validates that .env is untracked, .gitignore is properly configured, and placeholder values aren't committed to version control.

Yes. Execute this check as part of your pre-push or pre-deploy workflow to confirm no secrets are exposed in your JavaScript/TypeScript code. It validates git hygiene, scans for hardcoded credentials, and reports findings with actionable remediation steps before you push to GitHub.

Credential detection uses bash-based scanning with grep utilities to identify sensitive patterns in code and configuration files during pre-push stages. It checks for hardcoded API keys, real .env values, and improper .gitignore tracking, then generates a security report documenting exposure risks.

Yes. This security check applies to both backend and frontend JavaScript and TypeScript codebases, scanning for hardcoded credentials, validating environment file tracking, and verifying .gitignore configuration across your entire project structure.

When the scan detects exposed credentials, it generates a detailed security report documenting the findings and provides actionable remediation steps to remove secrets from code, update .gitignore, and prevent future credential leakage before deployment.