v9-deployment-verifier

Verify V9 deployment readiness and deployment regressions after changes to install scripts, Ansible roles, Helm charts, smoke checks, or middleware topology. Use when Codex modifies files under `install.sh`, `ansible/`, `helm-chart/`, `images/load-images.sh`, `foundation/`, `init-scripts/`, or deployment validation scripts and needs to run the standard local validation flow.

Jump to install

Repository: anybackup-ai/Anybackup
Last source activity: April 30, 2026 at 16:24
Detected SKILL.md language: English
Stars: 264
Forks: 59

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/anybackup-ai/Anybackup --skill v9-deployment-verifier

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

kweaver-core-offline-deploy

Use when executing or verifying the AnyBackup Agent release deployment flow with KWeaver Core, Foundation, sandbox, V9 infra, and business services.

2026-05-08

ag-ui-design

Use when an Agent must design user-visible AG-UI Markdown constraints before ag-ui-response publishes MQ, including layout, components, semantic labels, thought summaries, tool-call presentation, results, errors, clarification, and hidden-content boundaries.

2026-04-30

ag-ui-response

Use when an Agent must produce user-visible Markdown and wrap it into the Decision Agent MQ field payload.ag_ui.

2026-04-30

View all from this repository

V9 Deployment Verifier

Run the repository validator after every deployment-related change:

python scripts/validate_deploy.py --mode regression

Use release mode before claiming the package is customer-installable:

python scripts/validate_deploy.py --mode release

What the validator covers

Required deployment files exist.

install.sh still points to existing companion scripts.

Helm lint and template succeed for v9-infra, core-agent-service, v9-services, and the umbrella chart.

v9-infra renders all four middleware components.

core-agent-service still renders POSTGRES_URL, RABBITMQ_URL, REDIS_URL, and OPENSEARCH_URL.

Ansible syntax is checked when ansible-playbook is installed.

Missing local tools such as ansible-playbook, kubectl, docker, or bash are reported explicitly as skipped runtime checks.

How to interpret results

Treat any FAIL as a real regression or delivery blocker.

Treat WARN in regression mode as a follow-up item, not as proof of deployability.

Treat SKIP as "not verified on this machine"; mention the missing tool in the final response.

Do not say the deployment is fully verified if release mode fails or if runtime checks are skipped.

Guardrails

Prefer the validator script over ad hoc one-off checks.

If you change deployment logic, run the validator before replying.

If the validator cannot cover a runtime path because the machine lacks tooling or cluster access, say exactly which checks were skipped.

Keep the validator script updated when deployment entrypoints or expected middleware components change.

name	v9-deployment-verifier
description	Verify V9 deployment readiness and deployment regressions after changes to install scripts, Ansible roles, Helm charts, smoke checks, or middleware topology. Use when Codex modifies files under `install.sh`, `ansible/`, `helm-chart/`, `images/load-images.sh`, `foundation/`, `init-scripts/`, or deployment validation scripts and needs to run the standard local validation flow.