Pre-deployment validation - checks build, tests, security, dependencies, and deployment config against target environment. Generates a deployment readiness report with go/no-go recommendation. Use before any deployment execution.
From popkit-opsnpx claudepluginhub jrc1883/popkit-ai --plugin popkit-opsThis skill uses the workspace's default tool permissions.
scripts/validate_deployment.pyDesigns and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Pre-deployment validation and readiness assessment. Ensures everything is in order before deploying.
Trigger: /popkit-ops:deploy validate or before any deployment execution
Purpose: Run comprehensive checks against the project and deployment configuration to catch issues before they reach production. Produces a go/no-go recommendation with a readiness score.
| Step | When | Decision ID |
|---|---|---|
| 1 | Before validation | scope_level |
| 2 | After results | proceed_action |
Skipping these violates PopKit UX standard.
| Check | Description | Blocking |
|---|---|---|
| Config exists | deploy.json present and valid | Yes |
| Target config | All enabled targets have required fields | Yes |
| Version check | Version field present and valid | Yes |
| Git status | Working directory clean (no uncommitted changes) | Warning |
| Check | Description | Blocking |
|---|---|---|
| Build | Project builds successfully | Yes |
| Tests | Test suite passes | Yes |
| Dependencies | No known vulnerable dependencies | Warning |
| Lockfile | Lock file present and up to date | Warning |
| ENV vars | Required environment variables documented | Warning |
| Check | Description | Blocking |
|---|---|---|
| Security scan | Static security analysis | Warning |
| License audit | Dependency license compatibility | Warning |
| Docker lint | Dockerfile best practices (hadolint) | Warning |
| K8s validate | Kubernetes manifest validation | Warning |
| Size check | Build artifact size within limits | Warning |
| Integration | Integration test suite passes | Yes |
python scripts/validate_deployment.py --dir . --action load-config
Loads deploy.json and reports current state.
Use AskUserQuestion:
- question: "What level of validation should I run?"
- header: "Scope"
- options:
- "Quick check" - Config and build only (~30s)
- "Standard (Recommended)" - Config, build, tests, deps (~2-5min)
- "Full validation" - All checks including security (~5-15min)
python scripts/validate_deployment.py --dir . --action validate --scope standard --target docker
Use AskUserQuestion:
- question: "Validation complete. How should I proceed?"
- header: "Results"
- options:
- "Proceed to deploy" - All passed, deploy now
- "Fix issues" - Address failures first
- "Deploy anyway" - Override warnings (not recommended)
- "Abort" - Do not deploy
Score is calculated from check results:
| Score | Meaning | Recommendation |
|---|---|---|
| 100 | All checks passed | GO - Deploy |
| 80-99 | Passed with warnings | GO - Deploy with awareness |
| 60-79 | Some non-blocking failures | CONDITIONAL - Fix warnings first |
| 40-59 | Significant issues | NO-GO - Fix before deploying |
| 0-39 | Critical failures | NO-GO - Blocking issues |
Deployment Validation
=====================
Target: docker (primary)
Scope: standard
Environment: production
Checks:
[PASS] Config valid
[PASS] Build succeeds
[PASS] Tests pass (142/142)
[WARN] 2 moderate vulnerabilities in dependencies
[PASS] Lock file up to date
[WARN] .env.example missing DATABASE_URL
Score: 85/100
Recommendation: GO (with warnings)
Warnings:
1. npm audit: 2 moderate vulnerabilities (run npm audit fix)
2. .env.example incomplete: DATABASE_URL not documented
Next: /popkit-ops:deploy execute --target docker
Called by:
/popkit-ops:deploy validate commandpop-deploy-setup workflow (validate step)pop-deploy-execute workflow (pre-deploy validation)Triggers:
Followed by:
pop-deploy-execute - Execute the deploymentpop-deploy-setup - Fix configuration issues| Component | Relationship |
|---|---|
pop-deploy-init | Creates deploy.json config |
pop-deploy-setup | Generates deployment files |
pop-deploy-execute | Executes deployment |
deployment-validator | Agent for automated validation |