Skip to main content
skill CX Codex

preview-environments-builder — Claude Code skill: guide

preview-environments-builder sets up ephemeral preview environments for pull requests with automated deployments, unique URLs, and automatic cleanup once a PR closes.

MIT 250 installs ★ 64 updated 2026-01-12

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add patricio0312rev/skills --skill preview-environments-builder -a claude-code
Open on GitHub

What preview-environments-builder does

This skill supplies GitHub Actions workflows for spinning up temporary environments on every pull request. It includes blueprints for Vercel deployments alongside Docker and Kubernetes setups. Workflows create isolated targets, comment on the pull request with the generated URL, and remove stale resources when the branch merges or closes.

It also outlines URL conventions and preview database initialization via psql. Without configured tokens such as VERCEL_TOKEN or Kubernetes cluster credentials in GitHub secrets, deployment jobs will fail.

What it helps with

  • create temporary preview environments for pull requests
  • post preview deployment URLs directly to pull request comments
  • tear down Kubernetes namespaces and deployments when a PR closes
  • provision and seed isolated preview databases

Example prompts for the agent

  • Create a GitHub Actions workflow to deploy PR previews to Vercel
  • Set up ephemeral Kubernetes environments with automatic cleanup on PR close
  • Add a workflow step to seed a temporary database for review apps

How to install preview-environments-builder

1Skills CLI (Vercel)

npx skills add patricio0312rev/skills --skill preview-environments-builder -a claude-code

2Manually: put the files in place

~/.claude/skills/preview-environments-builder/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/preview-environments-builder/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about preview-environments-builder

How to install preview-environments-builder in Claude Code?

Run npx skills add patricio0312rev/skills --skill preview-environments-builder -a claude-code.

What does preview-environments-builder do?

It provides workflow templates to launch ephemeral preview deployments on Vercel or Kubernetes for each pull request.

How does cleanup work when a pull request closes?

A dedicated workflow triggers on PR closure to delete Vercel deployments or remove the preview Kubernetes namespace.

Source text

SKILL.md · MIT
---
name: preview-environments-builder
description: Creates ephemeral preview deployments for each pull request with automatic deployment, unique URLs, and cleanup on PR close. Use for "preview deployments", "PR environments", "ephemeral environments", or "review apps".
---

# Preview Environments Builder

Deploy isolated preview environments for every pull request.

## Vercel Preview Deployment

```yaml
# .github/workflows/preview.yml
name: Preview Deployment

on:
  pull_request:
    types: [opened, synchronize, reopened]

jobs:
  deploy-preview:
    runs-on: ubuntu-latest
    environment:
      name: preview-${{ github.event.pull_request.number }}
      url: ${{ steps.deploy.outputs.url }}

    steps:
      - uses: actions/checkout@v4

      - uses: actions/setup-node@v4
        with:
          node-version: "20"
          cache: "npm"

      - run: npm ci
      - run: npm run build

      - name: Deploy to Vercel
        id: deploy
        uses: amondnet/vercel-action@v25
        with:
          vercel-token: ${{ secrets.VERCEL_TOKEN }}
          vercel-org-id: ${{ secrets.VERCEL_ORG_ID }}
          vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID }}
          scope: ${{ secrets.VERCEL_ORG_ID }}
          alias-domains: pr-${{ github.event.pull_request.number }}.myapp.dev

      - name: Comment PR
        uses: actions/github-script@v7
        with:
          script: |
            github.rest.issues.createComment({
              issue_number: context.issue.number,
              owner: context.repo.owner,
              repo: context.repo.repo,
              body: `✅ Preview deployed!\n\n🔗 **URL:** ${{ steps.deploy.outputs.url }}\n\nCommit: ${context.sha.substring(0, 7)}`
            })
```

## Docker-based Preview

```yaml
preview:
  runs-on: ubuntu-latest
  steps:
    - uses: actions/checkout@v4

    - name: Build Docker image
      run: |
        docker build -t myapp:pr-${{ github.event.pull_request.number }} .

    - name: Deploy to Kubernetes
      run: |
        kubectl create namespace pr-${{ github.event.pull_request.number }} || true
        kubectl apply -f k8s/preview.yml \
          --namespace pr-${{ github.event.pull_request.number }}
        kubectl set image deployment/myapp \
          myapp=myapp:pr-${{ github.event.pull_request.number }} \
          --namespace pr-${{ github.event.pull_request.number }}

    - name: Get preview URL
      id: url
      run: |
        URL=$(kubectl get ingress myapp \
          --namespace pr-${{ github.event.pull_request.number }} \
          -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
        echo "url=https://pr-${{ github.event.pull_request.number }}.preview.myapp.com" >> $GITHUB_OUTPUT

    - name: Comment PR
      uses: actions/github-script@v7
      with:
        script: |
          github.rest.issues.createComment({
            issue_number: context.issue.number,
            owner: context.repo.owner,
            repo: context.repo.repo,
            body: `🚀 Preview deployed to: ${{ steps.url.outputs.url }}`
          })
```

## Cleanup on PR Close

```yaml
# .github/workflows/cleanup-preview.yml
name: Cleanup Preview

on:
  pull_request:
    types: [closed]

jobs:
  cleanup:
    runs-on: ubuntu-latest
    steps:
      - name: Delete Vercel deployment
        uses: actions/github-script@v7
        with:
          github-token: ${{ secrets.GITHUB_TOKEN }}
          script: |
            const deployments = await github.rest.repos.listDeployments({
              owner: context.repo.owner,
              repo: context.repo.repo,
              environment: `preview-${context.issue.number}`
            });

            for (const deployment of deployments.data) {
              await github.rest.repos.createDeploymentStatus({
                owner: context.repo.owner,
                repo: context.repo.repo,
                deployment_id: deployment.id,
                state: 'inactive'
              });

              await github.rest.repos.deleteDeployment({
                owner: context.repo.owner,
                repo: context.repo.repo,
                deployment_id: deployment.id
              });
            }

      - name: Cleanup Kubernetes namespace
        run: |
          kubectl delete namespace pr-${{ github.event.pull_request.number }} --ignore-not-found=true
```

## Environment Naming

```yaml
# Consistent naming pattern
environment:
  name: preview-pr-${{ github.event.pull_request.number }}
  url: https://pr-${{ github.event.pull_request.number }}.preview.myapp.com
```

## Database Seeding

```yaml
- name: Setup preview database
  run: |
    # Create database
    psql -c "CREATE DATABASE preview_pr_${{ github.event.pull_request.number }};"

    # Seed with test data
    npm run db:seed -- --database=preview_pr_${{ github.event.pull_request.number }}
  env:
    DATABASE_URL: ${{ secrets.PREVIEW_DB_URL }}
```

## Best Practices

1. **Unique URLs**: pr-{number}.preview.domain.com
2. **Auto cleanup**: Delete on PR close
3. **Comment on PR**: Link to preview
4. **Environment protection**: Require approval
5. **Resource limits**: Prevent abuse
6. **TTL**: Auto-delete after 7 days
7. **Secrets management**: Use preview-specific secrets

## Output Checklist

- [ ] Preview deployment workflow
- [ ] Unique URL generation
- [ ] PR comment with link
- [ ] Cleanup workflow on close
- [ ] Environment naming strategy
- [ ] Database seeding (if needed)
- [ ] Resource limits configured

© patricio0312rev · MIT · patricio0312rev/skills

Similar skills

All skills for DevOps and infrastructure →

From the same set148

The whole set →
test-reporting-triage-skill test-reporting-triage-skill sorts test failures into categories, suggests likely owners and lists next steps. Useful when you need a structured readout of a test run. CX Codex +1 257installs mocking-assistant mocking-assistant generates reliable mock setups for APIs, services, and UI components using MSW conventions and Vitest testing patterns. CX Codex +1 256installs service-layer-extractor service-layer-extractor refactors bloated route handlers into dedicated services and repositories. Separates business logic from HTTP transport and simplifies unit testing. CX Codex +1 255installs rag-pipeline-builder rag-pipeline-builder designs a retrieval-augmented pipeline for a document assistant: chunking, metadata, hybrid search, reranking and a way to measure retrieval quality. CX Codex +1 251installs load-test-scenario-builder load-test-scenario-builder generates load testing plans, k6 automation scripts, traffic models, and threshold criteria to check service capacity. CX Codex +1 236installs graphql-schema-designer graphql-schema-designer is a Claude Code skill for shaping GraphQL APIs with types, queries, mutations, subscriptions, and resolvers. It activates for requests about schema design, GraphQL setup, or Apollo Server. CX Codex +1 230installs test-data-factory-builder The test-data-factory-builder Claude Code skill builds factories and builders for test data. It activates for requests about fixture factories, test data builders, or generating related records. CX Codex +1 229installs terraform-module-builder terraform-module-builder generates structured, reusable Terraform modules with input variable validation, outputs, and example configurations. CX Codex +1 229installs

Project sponsors

Companies that keep this analytics open