skills.rest
wagnerra23
wagnerra23COMMUNITY
Explore all skills by this author →
GitHub

smoke-prod-evidence

Verify production deployments with curl -sv hop-by-hop status codes and redirect Locations.

Updated May 14, 2024
Search Tags:#deployment verification#http status codes#redirect validation#production smoke#curl -sv#middleware regression
One-click install
npx skills add https://github.com/wagnerra23/oimpresso.com --skill smoke-prod-evidence
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-prod-evidence
Source: https://github.com/wagnerra23/oimpresso.com/tree/main/.claude/skills/smoke-prod-evidence
Command: npx skills add https://github.com/wagnerra23/oimpresso.com --skill smoke-prod-evidence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents premature claims like “it’s working” by requiring unambiguous production evidence using curl -sv status codes and redirect hops, especially after deploys and runtime-critical edits.

Core Features & Use Cases

  • Production-first verification: Checks that redirect, middleware, routing, cache/assets, and web-server behavior work in the real prod environment (not just local smoke).
  • Evidence-grade curl output: Enforces literal hop-by-hop status codes and locations (e.g., 301/302/200) rather than relying on redirect counts or “final URL” outcomes.
  • Regression-adjacent testing: Validates that changes to one path do not break similar neighboring routes or login/auth flows.
  • Honest failure messaging: Produces compliant, non-overconfident responses when evidence is missing, including a clear “prod not verified yet” stance.

Quick Start

Ask to verify the fix by running the prod smoke protocol with curl -sv for the relevant paths you changed, including one negative case and one adjacent regression case, and return the collected status-code hop evidence.

Frequently Asked Questions about smoke-prod-evidence

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

FAQPage Schema
How do I verify production redirects using curl -sv hop-by-hop status codes?▼

Production redirect verification using curl -sv involves capturing literal hop-by-hop HTTP status codes and redirect Locations, ensuring every 301, 302, and 200 response is explicitly documented rather than relying on redirect counts or final URL outcomes.

What is production smoke testing for deployment verification?▼

Production smoke testing for deployment verification is the process of proving runtime readiness in the real prod environment by testing routing, middleware, caches, and web-server behavior using explicit HTTP evidence instead of local environment assumptions.

When should I run middleware regression tests after a deploy?▼

You should run middleware regression tests after deploys, merges, runtime-critical file edits, and troubleshooting to validate that changes to one path do not break neighboring routes, login flows, or web-server behavior in production.

How do I document an evidence missing response when prod is not verified?▼

When prod is not verified, you document an evidence missing response by outputting a compliant, non-overconfident message that clearly states prod is not verified yet, rather than prematurely claiming the deployment is working.

Does curl -sv redirect validation work for OPcache and asset bundle checks?▼

Yes, curl -sv redirect validation works for OPcache and asset bundle checks by capturing explicit HTTP status codes and Locations, verifying that routing, caches, and web-server behavior function correctly in the production environment.

Related Skills

Explore More Software Engineering Skills→
ngochuy13ngochuy13

api-tester

Execute HTTP requests and validate REST API responses across success and failure scenarios.

Community
Advanced
mr-daedaliummr-daedalium
107

land-and-deploy

Merge PRs, trigger deployment, and verify canary health in CI/CD pipelines.

Community
Advanced
intersystems-communityintersystems-community
27

objectscript-debugging

Diagnose IRIS runtime and compile errors using diagnostic packets and source mapping.

Official
Advanced
giljaegiljae
1

gstack-canary

Monitor live web apps for console errors, performance, and visual regressions post-deploy.

Community
Intermediate