env-health-check

Audit SpawnForge production environments for deployment and runtime issues.

5|1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/Tristan578/project-forge --skill env-health-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env-health-check
Source: https://github.com/Tristan578/project-forge/tree/main/.claude/skills/env-health-check
Command: npx skills add https://github.com/Tristan578/project-forge --skill env-health-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Production environments can silently fail due to broken CD pipelines, missing environment variables, or unresponsive health/status endpoints. This skill performs a comprehensive health check across deployment pipelines, health APIs, and staging parity to surface issues before they impact customers.

Core Features & Use Cases

  • Checks CD Pipeline Status to confirm the last runs are healthy and actionable.
  • Verifies Vercel Deployment Freshness to ensure production aligns with the latest main commits.
  • Validates Production Health API and Status API responses for availability and correctness.
  • Performs Critical Pages HTTP checks to verify key endpoints respond correctly.
  • Assesses Sentry for unresolved issues to surface critical incidents.
  • Provides a Staging vs Production comparison to confirm deployments and commits are in sync.

Quick Start

Run the health check to verify production readiness and surface issues across CI/CD, deployments, and health endpoints.

Frequently Asked Questions about env-health-check

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

FAQPage Schema
How do I perform a production health check after a Vercel deployment?

To perform a production health check, verify CI/CD pipeline status, confirm Vercel deployment freshness against main commits, and validate health endpoint responses. This surfaces deployment and runtime issues like broken pipelines or missing variables before they impact customers.

What does a staging vs production environment comparison check for?

A staging vs production comparison verifies that deployments and commits are in sync across both environments. This environment parity check ensures staging accurately reflects production, preventing untested changes from reaching live customers.

Can I check Sentry for unresolved production issues during a health audit?

Yes, a comprehensive health audit assesses Sentry for unresolved issues to surface critical incidents. This error visibility check identifies runtime exceptions and production errors that require immediate investigation.

How do I verify CD pipeline status and deployment integrity?

Verifying CD pipeline status involves checking that the last continuous deployment runs are healthy and actionable. This deployment integrity validation confirms production aligns with the latest main commits and has no silent pipeline failures.

Does this health check validate production health API and status API responses?

Yes, this health check validates production health API and status API responses for availability and correctness. It also performs HTTP checks on critical pages to verify key endpoints respond correctly to traffic.

When do I need to run an end-to-end validation for deployment integrity?

You need end-to-end validation during post-deploy checks, session startups, and infrastructure changes. Running a health check at these points verifies environment parity, error visibility, and deployment integrity across staging and production.