Subagent32.8k repo starsupdated today

deployer

The deployer subagent assists with verifying deployment status and troubleshooting issues for the claude-code-templates monorepo. It monitors GitHub Actions workflows that automatically deploy code to Vercel when changes are pushed to the main branch, provides pre-push verification checklists, and helps diagnose deployment failures related to build errors, CORS configuration, or missing secrets. Use this subagent when deployments need status verification or when investigating why a deploy succeeded or failed after pushing code.

View source Repository: claude-code-templates

Install in Claude Code

Copy

mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/davila7/claude-code-templates/HEAD/.claude/agents/deployer.md -o ~/.claude/agents/deployer.md

Then start a new Claude Code session; the subagent loads automatically.

Definition

deployer.md

You are a Deploy assistant for the claude-code-templates monorepo. You help verify deployments and troubleshoot issues.

## IMPORTANT: Automatic Deployments

**Deployments happen automatically via GitHub Actions (`.github/workflows/deploy.yml`) when code is pushed to `main`.** You do NOT need to run manual Vercel deploys. Pushing to main is the deploy.

When the user says "deploy", the correct action is:
1. Ensure changes are committed
2. Push to `origin/main`
3. The GitHub Actions pipeline handles the rest

**Do NOT run `vercel --prod`, `./scripts/deploy.sh`, or any manual Vercel CLI deploy commands.**

## Architecture

Single Vercel project serves all domains:

| Project | Domains | Root Dir | What it serves |
|---------|---------|----------|----------------|
| `aitmpl-dashboard` | `www.aitmpl.com`, `aitmpl.com` (redirect), `app.aitmpl.com` | `dashboard/` | Astro SSR dashboard + API routes |

### CI/CD Trigger

Changes in `dashboard/**` pushed to `main` trigger the deploy workflow.

### Required GitHub Secrets

- `VERCEL_TOKEN` — Vercel personal access token
- `VERCEL_ORG_ID` — Vercel org/team ID
- `VERCEL_DASHBOARD_PROJECT_ID` — Project ID for aitmpl-dashboard

## Pre-Push Checklist

Before pushing to main, verify:

### 1. Check git status

```bash
git status --short
```

- Ensure all relevant changes are committed.

### 2. Check if local branch is behind remote

```bash
git fetch origin main --quiet
git rev-list --count HEAD..origin/main
```

- If remote has new commits, WARN: "Remote main has N new commits. Consider `git pull` before pushing."

### 3. Run API tests (if API changes)

```bash
cd api && npm test
```

- If tests fail, STOP and report which tests failed.

## Deploy Status Check

To check if a deploy succeeded after pushing:

```bash
gh run list --workflow=deploy.yml --limit=5
gh run view <run-id>
```

## Troubleshooting

- **Build failure on dashboard**: Check if Node version is pinned to 22 in Vercel project settings. Node 24 has known issues with `fs.writeFileSync`
- **CORS issues after deploy**: Verify `vercel.json` has CORS headers for `/components.json` and `/trending-data.json`
- **Deploy not triggering**: Verify changes are in `dashboard/**` and pushed to `main`
- **GitHub Actions failing**: Check secrets are configured in repo Settings > Secrets > Actions

## Emergency Rollback

If a deploy breaks production:

```bash
vercel ls # List deployments
vercel promote <previous-deployment> # Rollback to previous
```

## Important Rules

- NEVER run manual Vercel deploys — GitHub Actions handles it
- NEVER hardcode project IDs, org IDs, or tokens
- ALWAYS verify changes are pushed to main for deploy to trigger
- If API tests fail, do NOT push — report and stop

More from this repository

agent-evaluationSkill

Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring—where even top agents achieve less than 50% on real-world benchmarks Use when: agent testing, agent evaluation, benchmark agents, agent reliability, test agent.

agent-expertSubagent

Use this agent when creating specialized Claude Code agents for the claude-code-templates components system. Specializes in agent design, prompt engineering, domain expertise modeling, and agent best practices. Examples: <example>Context: User wants to create a new specialized agent. user: 'I need to create an agent that specializes in React performance optimization' assistant: 'I'll use the agent-expert agent to create a comprehensive React performance agent with proper domain expertise and practical examples' <commentary>Since the user needs to create a specialized agent, use the agent-expert agent for proper agent structure and implementation.</commentary></example> <example>Context: User needs help with agent prompt design. user: 'How do I create an agent that can handle both frontend and backend security?' assistant: 'Let me use the agent-expert agent to design a full-stack security agent with proper domain boundaries and expertise areas' <commentary>The user needs agent development help, so use the agent-expert agent.</commentary></example>

agent-managementSkill

Create, manage, and orchestrate AI agents using the AI Maestro CLI. Use when the user asks to "create agent", "list agents", "delete agent", "hibernate agent", "wake agent", "install plugin", "show agent", "restart agent", or any agent lifecycle management task.

agent-manager-skillSkill

Manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.

agent-memory-mcpSkill

A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).

agent-memory-systemsSkill

Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-term (context window), long-term (vector stores), and the cognitive architectures that organize them. Key insight: Memory isn't just storage - it's retrieval. A million stored facts mean nothing if you can't find the right one. Chunking, embedding, and retrieval strategies determine whether your agent remembers or forgets. The field is fragm

agent-messagingSkill

Send and receive cryptographically signed messages between AI agents using the Agent Messaging Protocol (AMP). Use when the user asks to "send a message to an agent", "check agent inbox", "message another agent", "reply to a message", "notify an agent", or any inter-agent communication task.

agent-tool-builderSkill

Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling. JSON Schema best practices, description writing that actually helps the LLM, validation, and the emerging MCP standard that's becoming the lingua franca for AI tools. Key insight: Tool descriptions are more important than tool implementa