---
name: al-632-after-every-production-deploy-fire-a-claude-code-task-tha
description: "Anthropic’s Claude Code scheduled-tasks documentation lists deploy verification as a first-class example: the CD pipeline calls the task’s API /fire endpoint after each production deploy; the task runs smoke checks against the new build, scans error logs for regressions, and posts a go or no-go to the release channel before the deploy window closes. Pair it with branch protection and a human owner for rollback decisions. Feature is in research preview—confirm availability and usage limits on your plan before relying on it in a release train. Use when the user wants help with post-deploy smoke and go/no-go agent (operations) for a small business."
---

# After every production deploy, fire a Claude Code task that runs smoke checks, scans error logs, and posts a go / no-go to the release channel before the window closes

Anthropic’s Claude Code scheduled-tasks documentation lists deploy verification as a first-class example: the CD pipeline calls the task’s API /fire endpoint after each production deploy; the task runs smoke checks against the new build, scans error logs for regressions, and posts a go or no-go to the release channel before the deploy window closes. Pair it with branch protection and a human owner for rollback decisions. Feature is in research preview—confirm availability and usage limits on your plan before relying on it in a release train.

## Inputs to collect first
Ask the user for anything below that they haven't already given you. Don't guess missing facts.

- The material the task is about (pasted text, notes or data)

## Instructions

Do the task below with the user's inputs in place of each [bracket].

1. Write a one-page smoke checklist (health URL, login, one write path, error-rate threshold) and the exact go / no-go message format for your release channel.
2. Create a Claude Code cloud task with an API trigger whose prompt runs only that checklist, reads recent error logs, and posts the verdict—never rolls back by itself.
3. From your CD pipeline, POST to the Fire URL right after the production deploy succeeds, including the release id and URLs in the text payload.
4. Dry-run on staging until go/no-go matches what a human would have said.
5. Keep a named human as release owner: they read the verdict and trigger rollback if needed; the agent only reports.

## Safety checks (share these with the user)

- Read and edit the draft before it reaches a customer or goes public. If you later automate this prompt, start with "draft and notify me", not "send automatically".
- Check names, dates, numbers and any claim against your own source material before you use the answer. AI can misread or invent details.
- Say clearly which parts need a person to review or approve before anything is sent, paid, posted or filed.

## About this skill

- Works with: Claude Code cloud scheduled tasks (API trigger), CD/CI pipeline, app health endpoints + log store, Slack/Teams release channel
- Based on this real-world example: https://code.claude.com/docs/en/routines
- Free prompt from AgentPlaybook Real Estate: https://agentic-library.netlify.app/prompt/al-632-after-every-production-deploy-fire-a-claude-code-task-that-r/
- To install in an agent that supports Agent Skills, save this file as SKILL.md in a folder with the same name as `name` above (for example in your skills directory). Install steps for Claude.ai, Claude Code, Cursor and Codex: https://agentic-library.netlify.app/skills/