sf-prod

Verify production deployments by checking statuses, URL health, and error logs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/diane-defores/shipflow --skill sf-prod
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sf-prod
Source: https://github.com/diane-defores/shipflow/tree/main/skills/sf-prod
Command: npx skills add https://github.com/diane-defores/shipflow --skill sf-prod

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies the process of confirming the success and stability of a production deployment, integrating status checks, URL health evaluations, and log analysis to provide a comprehensive confidence signal.

Core Features & Use Cases

  • Deployment Status Verification: Checks if the latest deployment has succeeded via Vercel MCP, GitHub statuses, or other CI/CD indicators.
  • Live URL Health Check: Performs HTTP requests to confirm the live application is responsive and functioning as expected.
  • Log Collection and Analysis: Retrieves build, runtime, and error logs from providers like Vercel, PM2, or Doppler, then filters and identifies potential issues.
  • Use Case: A developer wants to automate the verification after deploying an update to ensure the app is running correctly before informing users.

Quick Start

Run sf-prod with your project URL or name to get an immediate health report on the latest production deployment.

Frequently Asked Questions about sf-prod

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

FAQPage Schema
How do I verify production deployment health after a CI/CD release?▼

Verifying production deployment health involves checking the latest deployment status, confirming live URL responsiveness via HTTP requests, and analyzing build or error logs to ensure runtime stability before notifying users.

Can I automate Vercel deployment verification in my GitHub CI/CD workflow?▼

Yes, you can automate Vercel deployment verification within GitHub CI/CD workflows by checking deployment statuses, evaluating live URL responsiveness, and filtering build logs to identify potential issues automatically after a release.

What is the best way to check live URL responsiveness and runtime logs after deploying?▼

The best way to check live URL responsiveness and runtime logs is to retrieve build and error logs from providers like Vercel, PM2, or Doppler, and perform HTTP requests to confirm the live application is functioning as expected.

Does this deployment verification approach work with PM2 and Doppler log providers?▼

Yes, this deployment verification approach works with PM2 and Doppler log providers, retrieving build, runtime, and error logs to filter and identify potential issues for stable release confidence.

Why does my production deployment show success but the live application is unresponsive?▼

A production deployment can show success while the live application is unresponsive due to runtime errors; checking live URL health via HTTP requests and analyzing runtime logs helps identify these post-build issues.