post-deploy

Run post-deploy smoke tests on health endpoints, auth flow, and data pipelines.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/Srujan0798/NRG --skill post-deploy-srujan0798
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-deploy
Source: https://github.com/Srujan0798/NRG/tree/main/.claude/skills/post-deploy
Command: npx skills add https://github.com/Srujan0798/NRG --skill post-deploy-srujan0798

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy verification prevents silent failures by automating health checks after deployments, ensuring systems are reachable and secure before production use.

Core Features & Use Cases

  • Smoke tests of health endpoints (/health, /health/db, /health/llm, /health/qdrant) to confirm service readiness after deploy.
  • Auth flow validation across multiple user personas to ensure authentication and access controls function correctly.
  • Basic post-deploy query pipeline and audit-chain checks to verify data paths and integrity.
  • Use case: After deploying a new release, run the verification to detect regressions and confirm all critical components initialize properly.

Quick Start

Run post-deploy with the target environment to validate health endpoints, authentication, and query processing.

Frequently Asked Questions about post-deploy

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

FAQPage Schema
How do I run post-deploy health checks after a new release?

Post-deploy health checks validate deployment integrity by running deterministic smoke tests against target environments, verifying service readiness for health endpoints, auth flows, and data pipelines before production use.

What is post-deploy verification and when do I need it?

Post-deploy verification prevents silent failures by automating health checks after deployments, ensuring systems are reachable and secure before production use. You need it to detect regressions and confirm critical components initialize properly.

Does post-deploy verification work with Docker and Python virtual environments?

Post-deploy verification requires Bash, curl, Docker, and a Python virtual environment to execute deterministic smoke tests in a repeatable manner. These dependencies are necessary to validate health endpoints and authentication flows.

Can I validate authentication flows and data pipelines during post-deploy checks?

Yes, post-deploy checks validate auth flow across multiple user personas and perform basic query pipeline and audit-chain checks to verify data paths and integrity under real post-deploy conditions.

What's the best way to smoke test health endpoints like /health and /health/db?

Smoke testing health endpoints is best handled by automating post-deploy checks for /health, /health/db, /health/llm, and /health/qdrant to confirm service readiness and detect regressions after deploying a new release.

Why does my deployment pass but health endpoints return errors?

Health endpoints returning errors indicate deployment health risks that post-deploy verification catches by running smoke tests under real conditions, validating critical components like /health endpoints, authentication, and data pipelines.