name: ops user-invocable: false description: Operations - deployment pipeline, CI/CD, git workflow, dependency management, code formatting, Vite build, and cross-package migrations. Use for deploying, CI configuration, git operations, branch strategy, dependency upgrades, formatting, build tooling, and release management. version: "1.1.0" status: active packages: ["all"] dependencies: ["contracts"] last_updated: "2026-04-12" last_verified: "2026-04-12"

Ops Skill

Unified operations guide covering deployment, CI/CD, git workflow, dependency management, and code formatting for the Green Goods monorepo.

Activation

Part 1: Quick Reference

Everyday Commands

bun format                   # Format workspace (Biome)
bun lint                     # Lint workspace (oxlint + forge fmt)
bun run test                 # Run all tests (CRITICAL: not `bun test`)
bun build                    # Build everything (respects dependency order)
bun dev                      # Start all services via PM2
bun dev:stop                 # Stop all services

# Full validation (run before committing or pushing)
bun format && bun lint && bun run test && bun build

Deployment Commands

# Contract deployment (ALWAYS use deploy.ts, never forge script)
bun script/deploy.ts core --network sepolia              # Dry run
bun script/deploy.ts core --network sepolia --broadcast  # Deploy
bun script/deploy.ts core --network sepolia --broadcast --update-schemas  # Deploy + schemas

# Production readiness
bun run verify:contracts       # Full: build + lint + tests + E2E + dry runs
bun run verify:contracts:fast  # Quick: skip E2E and dry runs

# Indexer
cd packages/indexer && bun run dev:docker     # Local Docker
docker compose -f docker-compose.indexer.yaml up -d  # Production

# Frontend
cd packages/client && bun build && vercel --prod
cd packages/admin && bun build && vercel --prod

Git Conventions

# Branch naming: type/description (kebab-case)
feature/hats-protocol-v2    feat/passkey-login    bug/admin-build-fix

# Commit format: type(scope): description
# Types: feat, fix, refactor, chore, docs, test, perf, ci
# Scopes: contracts, indexer, shared, client, admin, agent, claude
feat(contracts): add Hats Protocol v2 module
fix(client): resolve offline sync race condition

Dependency Commands

bun outdated                    # Check for outdated packages
bun update wagmi                # Update specific package
bun install --frozen-lockfile   # CI validation (catches drift)
bun audit                       # Security vulnerability scan

Migration Rule

For cross-package breaking changes, plan the work and create or update the owning feature hub first, then follow migration.md. Migration notes belong in that hub's reports/ directory, not in a separate global migrations folder.

Part 2: Deployment Pipeline

Deployment Order (MANDATORY)

1. contracts  --> Generates ABIs + deployment artifacts
2. indexer    --> Needs contract addresses + ABIs
3. shared     --> Needs contract artifacts (build only, not deployed)
4. client     --> Needs shared + indexer endpoint
5. admin      --> Needs shared + indexer endpoint

Cross-Package Dependency Map

contracts --> deployments/{chainId}-latest.json --> shared (ABIs)
                                                 \-> indexer (addresses)
shared --> hooks, types, utils --> client
                                \-> admin
indexer --> GraphQL endpoint --> client (queries)
                             \-> admin (queries)

deploy.ts CLI

Network Configuration

Deployment Artifacts

packages/contracts/deployments/
  11155111-latest.json   # Sepolia
  42161-latest.json      # Arbitrum
  42220-latest.json      # Celo
  31337-latest.json      # Localhost
  networks.json          # Network registry

Imported by @green-goods/shared for contract address resolution.

Reference Files

Anti-Patterns

Deployment

1. Never use forge script directly -- always use deploy.ts
2. Never deploy to mainnet without dry run -- always validate first
3. Never skip the deployment order -- contracts must deploy before indexer
4. Never create package-specific .env files -- single root .env only
5. Never modify config/schemas.json -- it defines production EAS schemas

CI/CD & Git

1. Never run all tests without path filters -- wastes CI minutes on unchanged packages
2. Never skip --frozen-lockfile in CI -- causes dependency drift
3. Never force push shared branches -- rewrites history others depend on
4. Never merge without CI passing -- required status checks exist for a reason
5. Never commit secrets -- check for .env, credentials, API keys

Dependencies & Formatting

1. Never install root deps for package-specific needs -- install in the correct package
2. Never update all deps at once without testing -- isolate changes
3. Never manually edit bun.lockb -- binary format, always regenerate
4. Never use Prettier alongside Biome -- they conflict; remove Prettier if found
5. Never manually sort imports -- Biome's organizeImports handles it

Decision Tree

What ops work?
|
+-- Deploying something? -----------> deployment.md
|     contracts / indexer / frontend
|
+-- CI/CD pipeline work? -----------> ci-cd.md
|     workflows / caching / gates
|
+-- Git operations? ----------------> git-workflow.md
|     branch / commit / merge / PR
|
+-- Dependency issues? -------------> dependency-management.md
|     install / update / lockfile
|
+-- Formatting / imports? ----------> biome.md
|     bun format / editor setup
|
+-- Breaking change / multi-package rollout?
|     --> migration.md
|     --> create or update the owning plan hub first
|
+-- Pre-commit validation? ---------> Quick Reference (Part 1)
      bun format && bun lint && bun run test && bun build

Related Skills

• contracts -- Solidity development patterns, testing, and build system
• testing -- TDD workflow, Vitest patterns, E2E with Playwright
• indexer -- Event handler development, schema design, Docker setup
• contracts -- ABI/storage/deployment implications for migrations
• plan -- Migration plan lifecycle and team coordination