gitscape.ai: Skill for Claude Code

Shipping and Launch

Overview

Every production deploy is a risk management exercise. Move fast by being deliberate: know what you're deploying, have a rollback plan, verify the system is healthy after deploy, and keep the blast radius small. The fastest way to ship is to have a clean rollback when things go wrong — not to avoid deploying.

When to Use

• Before any deployment to the Cloud Run production environment
• When deploying a feature that changes user-facing behavior
• When updating environment variables or secrets in GCP
• When rolling out a new API endpoint or removing an old one

Pre-Deploy Checklist

Run this before triggering any Cloud Build deploy:

Code Quality

• All tests pass locally: pytest tests/ -v
• No linting errors: ruff check api/
• TypeScript compiles: npx tsc --noEmit (in web/)
• No TODO: before deploy comments remaining

Security

• No secrets committed to git: git log --oneline -5 — check commit messages
• New environment variables are in GCP Secret Manager, not in cloudbuild.yaml as plaintext
• .env.example updated if new variables are required

Observability

• New endpoints have structured logging (start/complete/error)
• New endpoints log request_id for correlation

Documentation

• README.md updated if user-visible behavior changed
• New environment variables documented in .env.example
• ADR created if an architectural decision was made

Rollback Readiness

• Know the previous working Cloud Run revision: gcloud run revisions list
• Know the rollback command (see below)

Rollback Procedure

GitScape deploys to Cloud Run. Rolling back is instant:

# List revisions (most recent first)
gcloud run revisions list \
  --service=gitscape-api \
  --region=us-central1 \
  --format="table(name,status.conditions[0].status,spec.containerConcurrency,metadata.creationTimestamp)"

# Rollback: send 100% traffic to the previous revision
gcloud run services update-traffic gitscape-api \
  --to-revisions=PREVIOUS_REVISION_NAME=100 \
  --region=us-central1