From arn-infra
This skill should be used when the user says "verify deployment", "verify infra", "check deployment", "arn infra verify", "infra verify", "health check", "check health", "verify staging", "verify production", "is my deployment healthy", "check if deployment worked", "run health checks", "deployment verification", "check infrastructure", "validate deployment", "verify environment", "post-deployment check", "infra health", "check dns", "check ssl", "verify endpoints", "smoke test", "integration test", or wants to validate that a deployed environment is healthy and its resources match the expected state. This skill runs health checks, DNS verification, SSL validation, resource state comparison, and updates issue labels and environments.md with verification results.
npx claudepluginhub appsvortex/arness --plugin arn-infraThis skill uses the workspace's default tool permissions.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Builds 3-5 year financial models for startups with cohort revenue projections, cost structures, cash flow, headcount plans, burn rate, runway, and scenario analysis.
Run post-deployment verification against a target environment to confirm that infrastructure is healthy, endpoints are reachable, DNS resolves correctly, SSL certificates are valid, and resource state matches the expected topology. Updates issue labels and environments.md with verification results.
This skill invokes the arn-infra-verifier agent to perform the actual health checks and produces a structured verification report.
Read ## Arness from the project's CLAUDE.md. If no ## Arness section exists or Arness Infra fields are missing, inform the user: "Arness Infra is not configured for this project yet. Run /arn-infra-wizard to get started — it will set everything up automatically." Do not proceed without it.
Check the Deferred field. If Deferred: yes, inform the user: "Infrastructure is in deferred mode. Verification is not available until infrastructure is fully configured. Run /arn-infra-assess to un-defer." Stop.
Extract:
~/.arness/user-profile.yaml (or .claude/arness-profile.local.md if it exists — project override takes precedence). Apply the experience derivation mapping from ${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-ensure-config/references/experience-derivation.md. If no profile exists, check for legacy Experience level in ## Arness as fallback.environments.md for deployment stateactive-resources.json for expected resource statetooling-manifest.json for available CLIsproviders.md## Arness config, for locating handoff files (default: .arness/infra-specs)Ask the user which environment to verify (if not specified in the invocation):
"Which environment would you like to verify? [list environments from config]"
Read the environment's deployment state from environments.md:
Last deployed is -- (never deployed): inform the user: "The [environment] environment has not been deployed yet. Run /arn-infra-deploy first." Stop.Collect the expected state from multiple sources:
2a. Resource manifest:
Read the resource manifest (active-resources.json):
Read <resource-manifest-path>
Filter resources for the target environment. Extract:
2b. Handoff file:
Look for the handoff file for the target environment:
Glob <specs-dir>/INFRA_HANDOFF_<environment>*
If found, read it and extract:
2c. INFRA spec:
Look for the infrastructure architecture spec:
Glob <specs-dir>/INFRA_*
If found, read it for the expected resource topology (resource types, counts, configurations).
If no expected state is available:
Warn: "No resource manifest or handoff file found for [environment]. I can still run basic health checks if you provide endpoint URLs. Would you like to provide URLs manually, or run /arn-infra-deploy first?"
If the user provides URLs manually, proceed with those as the expected state.
Read the local override or plugin default for
health-check-patterns.md.
Invoke the arn-infra-verifier agent via the Task tool with:
--- EXPECTED STATE --- Resources: [filtered resource manifest for the target environment] Endpoints: [list of endpoints with health check paths] DNS names: [list of DNS names with expected targets] SSL domains: [list of HTTPS domains requiring certificate validation] --- END EXPECTED STATE ---
--- PROVIDER CONTEXT --- Provider(s): [from providers.md] Available CLIs: [from tooling manifest -- which CLIs can query resource state] Environment: [target environment name] --- END PROVIDER CONTEXT ---
--- TOOLING --- Available tools: [list of installed verification tools from tooling manifest] curl: [available/unavailable] dig/nslookup: [available/unavailable] openssl: [available/unavailable] Provider CLIs: [list with auth status] --- END TOOLING ---
--- INSTRUCTIONS --- Run the following verification checks in order:
Produce a structured verification report with overall PASS/WARN/FAIL verdict. --- END INSTRUCTIONS ---
Read the verification report from the agent. Parse the overall status: PASS, WARN, or FAIL.
Read
${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-verify/references/verification-report-template.mdfor the expected report format.
On PASS:
Present the verification results to the user: "Verification PASSED for [environment]. All health checks, DNS, SSL, and resource state checks succeeded."
Update issue labels (if issue tracking is configured):
arn-infra-verifiedarn-infra-failed (if present from a previous failed attempt)Update active-resources.json:
lastVerified to the current ISO 8601 timestamp for all resources in the target environmentUpdate environments.md:
- **Last verified:** [ISO 8601 timestamp]
- **Verification status:** PASS
On WARN:
Present the verification results with warnings: "Verification completed with WARNINGS for [environment]. The deployment is functional but the following issues were detected: [list warnings]."
Update issue labels:
arn-infra-verified (functional despite warnings)Update active-resources.json:
lastVerified to the current timestampUpdate environments.md:
- **Last verified:** [ISO 8601 timestamp]
- **Verification status:** WARN ([summary])
On FAIL:
Present the verification results with failures: "Verification FAILED for [environment]. The following critical checks failed: [list failures]."
Categorize failures:
Suggest remediation for each failure:
/arn-infra-deploy to reconcile."/arn-infra-define and re-deploy."Adapt remediation detail to experience level:
Update issue labels:
arn-infra-failedarn-infra-verified (if present)Update environments.md:
- **Last verified:** [ISO 8601 timestamp]
- **Verification status:** FAIL ([failure summary])
Do NOT update lastVerified in active-resources.json (verification did not pass)
Offer remediation options:
Ask (using AskUserQuestion):
"How would you like to handle the verification failures?"
Options:
/arn-infra-deploy rollback procedures/arn-infra-deployPresent the verification summary:
"Verification Summary:
Files updated:
Recommended next steps:
[If PASS:]
/arn-infra-deploy targeting the next environment in the pipeline/arn-infra-monitor to configure observability/arn-infra-pipeline to automate future deployments[If WARN:]
/arn-infra-verify again after addressing warnings[If FAIL:]
/arn-infra-deploy/arn-infra-verify after fixesOr run /arn-infra-wizard for the full guided pipeline."
## Arness config missing: Suggest running /arn-infra-wizard to get started. Stop./arn-infra-deploy. Stop./arn-infra-discover."lastVerified in the resource manifest. Issue labels are updated idempotently.