Results for “health-check”

Provides deployment strategies, CI/CD pipeline patterns, Docker containerization best practices, health checks, and production readiness guidance for web applications.

Audits and repairs Markdown link health across a skills repo via a four-tier pipeline (config hardening, intra-repo file-ref fixes, external URL substitutions, residual exclusions) and enforces a Tier 3 substitution guardrail that prevents regressions of previously-passing links; designed for lychee-based GitHub Actions link checkers but generalizes to markdown-link-check and similar tools. Use when the request mentions link audit, dead links, link health, lychee, broken links, link checker, markdown link audit, link-health audit, 404 audit, check-links failing, CI link-check, or 連結健檢, 死鏈, 失效連結, 斷鏈檢查. Part of the AlterLab Academic Skills suite.

Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.

Analyze NATS clusters with read-only operations: discover JetStream streams and consumers, check cluster health, and inspect message flow.

Inspect and manage Envoy proxy configuration, cluster health, route tables, and performance stats via the admin API.

Validates the integrity of a project's .planning/ directory, reporting missing files, invalid configurations, and inconsistent state, with optional auto-repair of safe issues.

Monitors and analyzes etcd clusters: checks endpoint health, member status, alarms, key-space usage, leases, and Raft consensus state, then reports issues and recommendations.

Managing dependencies, CI/CD optimization, Docker configuration, and operational observability (logging/alerting/health checks). Use for build errors or dev environment issues.

Diagnoses Redpanda broker and cluster health using debug bundles, metrics endpoints, logs, CPU profiling, and partition/raft checks, with triage playbooks for common failure modes.

Detects the project stack and generates production-ready multi-stage Dockerfiles with compose services, .dockerignore, non-root users, health checks, layer caching, and optional dev hot-reload profiles.

Monitors a deployed URL for regressions after releases by checking HTTP status, console errors, network failures, performance metrics, content integrity, API health, static assets, and SSE streams.

Monitors, analyzes, and optimizes Apache Solr instances and SolrCloud clusters through a discovery-first workflow that checks cluster health, collection status, schema fields, cache hit ratios, and query handler performance.

Post-deploy smoke test combining all 5 tools (Sentry + Supabase + Firecrawl MCPs, plus the Langfuse and Playwright CLIs) into one workflow. Use when asked to: "verify deploy", "post-deploy check", "smoke test production", "check if deploy is healthy", "ship or rollback", "post-release check", "verify release", "deploy.

Debug running Docker containers and Compose services. Use when inspecting container logs, exec-ing into running containers, diagnosing networking issues, checking resource usage, debugging multi-stage builds, troubleshooting health checks, or fixing Compose service dependencies.

Full test suite improvement composite — audit health, prune dead tests, validate with mutation testing, capture rationale in ADR. Use after a major feature ship, before tightening coverage gates, or when the suite shows bloat, excessive skips, or slow runtime. Chains test-health → test-cleanup → mutation-test → adr-write.

Systematic audit of all installed tools, packages, and dependencies for available updates. Covers Homebrew, pip, npm/pnpm, system software updates, git repos, and key CLI tools. Run when the user asks "check if anything needs updating" or similar maintenance queries.

Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "timeout strategy", "deployment pipeline", "chaos engineering", "bulkhead pattern", "retry with backoff", or "health checks". Also trigger when designing resilient microservices, planning zero-downtime deployments, or investigating cascading failure scenarios. Covers capacity planning, health checks, and anti-fragility patterns. For data systems, see ddia-systems. For system architecture, see system-design.

Validate multi-skill workflows by checking skill existence, inter-skill data contracts, JSON schema compatibility, file naming conventions, and handoff integrity.

Operate a Redpanda cluster's health, brokers, configuration, and maintenance from the CLI using the `rpk cluster` command group, the front-end to the Admin API. Use when checking cluster health or metadata, decommissioning or recommissioning brokers, getting or setting cluster config properties, balancing or moving.

Generates CI/CD pipelines, Terraform modules, and Kubernetes deployment manifests with health-check gates and rollback support for AWS, GCP, and Azure.

Deploy, debug, and operate the RTVI-CV 2D detection/tracking microservice and call its REST API for stream management, health checks, and metrics.

Sets up DNS records, SSL/TLS certificates, subdomains, email authentication, and health-check failover routing for Route53, Cloudflare, or GCP Cloud DNS, with optional Terraform output.

Validate Azure deployments against functional, security, performance, and operational criteria before production release. Use this skill when users ask for readiness checks, health verification, or production sign-off gates. Covers Well-Architected Framework validation, SLA verification, and release readiness.

Land and deploy workflow. Merges the PR, waits for CI and deploy, verifies production health via canary checks. Takes over after /ship creates the PR. Use when: "merge", "land", "deploy", "merge and verify", "land it", "ship it to production". (gstack)

Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic. Use when: "setup deploy", "configure deployment", "set up land-and-deploy", "how do I deploy with gstack", "add deploy config".

Turn "what's happening with this account?" into a structured read straight from your CRM. A real-activity audit across every source, a qualification-vs-stage gap check, a one-screen account summary, and a risk verdict on the deal. Built for any sales team, customizable to your CRM and your sales process. Trigger on "analyze this account", "what's happening with this deal", "is this opp healthy", "what's stuck in my pipeline", "deal autopsy on this closed-lost", "where am I missing qualification coverage", "prep me for this account", or any account, opp, or pipeline diagnostic.