UAT Deployment
Deploy merged code to an isolated local UAT environment with pre-flight checks and smoke tests.
Installation
- Make sure Claude is on your device and in your terminal.
Skills load from
~/.claude/skills/when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then runclaudein any terminal to verify.One-time setupnpm i -g @anthropic-ai/claude-codeAlready have it? Skip ahead.
- Paste into Claude Code or into your terminal.
This copies the whole skill folder into
~/.claude/skills/agf-deploying-uat-pcliangx/— the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.Faster alternative (instruction-only skills)
Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.
Quick install (SKILL.md only)Sign up to copy - Restart Claude Code.
Quit and reopen Claude Code (or any other agent that loads from
~/.claude/skills/). New skills are picked up on startup. - Just ask Claude.
Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.
Prefer to read the source first? Open on GitHub.
When Claude uses it
Use when deploy-engineer is about to deploy the merged-to-main code to the isolated local UAT stack (after code review + SIT Audit pass and merge, before qa-engineer runs E2E/UAT). Provides the applicability gate, pre-flight checks, isolated compose bring-up (independent project name + port offset +900), in-container migration, real-output smoke test, hand-off, and the deploy-report skeleton. Pairs with deployment.md "UAT " contract and slash /agf-deploy-uat.
What this skill does
This skill guides deploy-engineers through deploying merged code from the main branch to an isolated local UAT environment. It enforces a strict runbook with pre-flight checks, containerized infrastructure setup with port isolation, database migrations, and smoke tests before handing off to QA. The deployment follows a binary pass/fail gate and produces a standardized report for handoff to the product lead.
What it does
- Applicability gate: Verifies the deployer is a deploy-engineer, the target is a full-stack web application (docker-compose), code review and SIT audit are complete and merged to main, and product-lead approval is confirmed.
- Pre-flight checks: Confirms main branch is clean and current, Docker daemon is running, the
.env.uatenvironment file exists and is gitignored, and the +900 port band (6332, 8900, 8980) is free. - Isolated stack bring-up: Uses a dedicated project name (
${APP_NAME}-uat) and port offset (+900) to ensure complete container, network, and volume isolation from dev and QA environments; rebuilds images with--build(never restart-only). - In-container migration: Runs
alembic upgrade headinside the backend container against the UAT database; captures and reports real migration output. - Smoke tests: Validates frontend reachability, backend health endpoint, core API responses, and database connectivity via real curl and psql commands—no dry-runs or "looks correct" assertions.
- Binary gate and handoff: Reports either ✅ deployment success (smoke passed) or ❌ deployment failure (with root cause: environment/config or code); sends report path and UAT service URLs to product-lead immediately.
How to use it
When the deploy-engineer is ready to deploy merged-to-main code to the isolated UAT stack after code review, SIT audit pass, and merge, invoke this skill by confirming the applicability gate (role, stack type, approval) and then work through each section in order: pre-flight checks, isolated compose bring-up with the project name and port offset, in-container migration, smoke test with real curl/psql output, and final binary verdict. Document all steps and real output in the deployment report skeleton (saved to docs/deploy/<feature>-uat-<YYYY-MM-DD>.md) and send a message to product-lead with the report path, UAT service URLs, and commit SHA.
Related skills
Documentation Co-Authoring
anthropics
Guide structured workflows for writing docs, proposals, and technical specs collaboratively.
MCP Server Builder
anthropics
Build protocol servers that connect language models to external APIs and services.
Skill Builder & Optimizer
anthropics
Create, edit, and optimize Claude skills with performance testing and benchmarking.
Multi-Component Web Artifacts
anthropics
Build complex React artifacts with Tailwind CSS and shadcn/ui components.