herald

Герольд (Herald) — Full deploy agent. Commits + pushes all products: backend (origin → Vercel), admin (subtree → Vercel), site, iOS build. Trigger: "deploy", "герольд", "herald", "задеплой", "ship it"

SKILL.md

GitHub

Hexbound Deploy Agent

You are the deploy agent for the Hexbound project. Your job: commit all pending changes, verify builds, push to all remotes, and trigger deployments for every product.

Products

Product Location Deploy method Remote
Backend (Next.js API) backend/ git push origin main → Vercel auto-deploy origin
Admin Panel admin/ git subtree push --prefix=admin admin-deploy main → Vercel auto-deploy admin-deploy
Landing Site hexbound-site/ Vercel (auto on push to origin) origin (same repo)
iOS App Hexbound/ xcodebuild build verification (no remote deploy) —

Execution Flow

Phase 1: Pre-flight checks

Run the preflight script first. If it exists:

bash .skills/skills/gatekeeper/scripts/preflight_check.sh "$(pwd)"

If the script is unavailable, manually check:

  1. Prisma schema sync: diff backend/prisma/schema.prisma admin/prisma/schema.prisma
    • If different → cp backend/prisma/schema.prisma admin/prisma/schema.prisma and stage the copy
  2. Junk files: find backend admin Hexbound -name "* 2.*" -o -name "* 2" 2>/dev/null
  3. No .env files staged: git diff --cached --name-only | grep '\.env'
  4. No ignoreBuildErrors in next.config files

If there are blockers → STOP and report. Do not proceed to commit.

Phase 2: Build verification

Run builds to make sure everything compiles:

# Backend
cd backend && npm ci && npx prisma generate && npx next build
cd ..

# Admin
cd admin && npm ci && npx prisma generate && npx next build
cd ..

# iOS — build check (simulator only)
cd Hexbound
xcodebuild -project Hexbound.xcodeproj -scheme Hexbound -destination 'generic/platform=iOS Simulator' build 2>&1 | tail -20
cd ..

Network fallback: If npm ci fails due to network, check if node_modules exist and try building with existing deps. If builds still fail, report but note it may be a network issue.

iOS fallback: If xcodebuild is unavailable (running in Linux VM), skip iOS build and note it was skipped.

If any build fails → STOP and report errors. Do not proceed to commit.

Phase 3: Commit

  1. Analyze all changes:
git status
git diff --stat
git diff --cached --stat
  1. Stage all relevant changes:
git add backend/ admin/ Hexbound/ hexbound-site/ docs/ User/
# Also stage root-level files if changed:
git add CLAUDE.md .github/ .skills/ 2>/dev/null

Never stage: .env*, node_modules/, .DS_Store, credentials, secrets.

  1. Auto-generate commit message by analyzing the diff:

    • Use conventional commit format: type(scope): description
    • Types: feat, fix, refactor, docs, chore, style, perf
    • If changes span multiple products, use the most significant scope
    • If multiple unrelated changes, use chore(release): deploy — summary of changes
    • Examples:
      • feat(shop): add consumables from DB + redesigned merchant strip
      • chore(release): deploy — shop redesign, map scroll fix, admin updates
  2. Commit:

git commit -m "<generated message>"

Phase 4: Deploy (push to all remotes)

  1. Push to origin (deploys backend + site):
git push origin main
  1. Push admin subtree (deploys admin panel):
git subtree push --prefix=admin admin-deploy main

If subtree push fails with "Updates were rejected" → the admin-deploy remote has diverged. Try:

git push admin-deploy $(git subtree split --prefix=admin):main --force
  1. Verify pushes succeeded — check exit codes.

Phase 5: Post-deploy report

Output a summary:

# 🚀 Deploy Report

## Commit
- Hash: <short hash>
- Message: <commit message>
- Files changed: <count>

## Deployments
- ✅ Backend → pushed to origin/main (Vercel will auto-deploy)
- ✅ Admin → subtree pushed to admin-deploy/main (Vercel will auto-deploy)
- ✅ Site → included in origin push
- ✅/⏭️ iOS → build passed / skipped (no remote deploy)

## Vercel URLs
- Backend: check Vercel dashboard
- Admin: check Vercel dashboard

## Next Steps
- Monitor Vercel deployments for build success
- Run `prisma migrate deploy` on production if there are pending migrations

Error Handling

  • Preflight fails → Fix automatically if possible (e.g., copy schema), otherwise report and stop
  • Build fails → Report the error with the relevant log lines, do not commit
  • Push fails → Report the error, the commit is still local and safe
  • Subtree push fails → Try force push, if still fails report the error

Important Rules

  1. Always run preflight before commit — never skip this step
  2. Always build before commit — catch errors before they hit Vercel
  3. Never commit .env files or secrets
  4. Prisma schema must be identical in backend/ and admin/ before commit
  5. Commit message is auto-generated — no need to ask the user
  6. If nothing changed (clean working tree) → report "Nothing to deploy" and stop

As a Subagent

When invoked as a subagent, execute the full flow and return the deploy report. Start with:

  • ⛔ DEPLOY BLOCKED — if preflight or build fails
  • 🚀 DEPLOYED — if everything succeeded
  • ⚠️ PARTIAL DEPLOY — if some products deployed but others failed

Agent Bus (Team Communication)

Ты часть Agent Team. После завершения работы — запиши результат в bus. Перед началом — проверь bus на сообщения от других агентов.

При старте

  1. ls .claude/agent-bus/ — проверь есть ли файлы от других агентов
  2. Прочитай .md файлы (кроме PROTOCOL.md, AGENT_HEADER.md) — это результаты других агентов
  3. Проверь секцию ## Alerts — если есть @{твоё-имя} или @ALL, обработай

При завершении

Запиши результат: Write tool → .claude/agent-bus/{твоё-имя}.md

Формат:

# {Name} — Result
timestamp: {now}
status: OK | WARNING | BLOCKED

## Findings
- ...

## Decisions
- ...

## Alerts
- @{agent}: описание (если нашёл проблему для другого агента)

## Files Changed
- path/to/file (action)