Ask Claude to Scaffold Production-Ready Health Check Endpoints
Load balancers, Kubernetes, and uptime monitors all need a health check endpoint to know when your app is ready to serve traffic. Claude can scaffold one that actually checks your dependencies, not just returns a 200.
Add a /health endpoint that checks: database connectivity with a lightweight query,
Redis availability with a ping, and disk space above 10% free. Return 200 OK with a
JSON status summary when healthy, or 503 Service Unavailable if any check fails.
Claude generates structured JSON responses that orchestrators understand:
{
"status": "degraded",
"services": {
"database": "healthy",
"redis": "unhealthy",
"disk": "healthy"
},
"uptime": 3842
}
For Kubernetes deployments, ask for separate liveness and readiness probes:
Add a /health/live endpoint that just confirms the process is running, and a
/health/ready endpoint that only passes once database migrations have completed
and the job queue has processed its backlog.
The distinction matters: liveness failures restart the container, readiness failures just stop routing traffic to it.
You can also ask Claude to add basic auth to the health endpoint so it isn't publicly explorable, or to include response time measurements for each dependency check.
A health endpoint is the cheapest thing you can add to prevent 3am incidents.
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.