// Execute a structured deployment to staging or production. Use when asked to deploy, ship, release, push to production, or promote to staging.
Design or review REST and GraphQL API interfaces. Use when asked to design an API, review endpoint structure, define request/response schemas, or improve API ergonomics.
Perform a structured security and quality audit on source code. Use when asked to review code, audit a pull request, check for vulnerabilities, or assess code quality.
Design, build, or debug data processing pipelines. Use when asked to process a dataset, transform data, build an ETL pipeline, schedule batch jobs, or fix data quality issues.
Safely run database schema migrations. Use when asked to update database schema, add columns, create tables, run alembic, or apply Django migrations.
Audit project dependencies for vulnerabilities, license issues, and bloat. Use when asked to check dependencies, audit packages, find vulnerable libraries, or reduce bundle size.
Write or update technical documentation for code, APIs, or systems. Use when asked to document a module, write a README, generate API docs, or update existing documentation.
| name | deploy-checklist |
| description | Execute a structured deployment to staging or production. Use when asked to deploy, ship, release, push to production, or promote to staging. |
| license | MIT |
| compatibility | Requires git and access to the deployment target |
| allowed-tools | Bash(git:*) Bash(docker:*) Bash(kubectl:*) |
You must have unambiguous answers to these before touching anything:
If the user says "deploy the thing" without specifying the environment, that is not sufficient information. Ask.
Model Proposes, Code Disposes: You propose the deploy sequence. The CI/CD system or platform CLI executes it. You do not write deployment commands from memory — you use exactly the command documented in the project's deploy runbook or Makefile.
git branch --show-current
git status --porcelain
git log --oneline main..HEAD to see what will be deployed. Present this to the user.Execute the deploy command. Use the project's existing deployment mechanism:
docker build && docker pushkubectl apply -ffly deploy, vercel --prod, gcloud run deploy
Use exactly the command documented in the project. Do not invent deployment commands.Wait for deployment to complete. Do not proceed until the deployment tool confirms success.
curl -s https://<deployed-url>/health | jq .
| Excuse | Rebuttal |
|---|---|
| "Tests are slow, I'll skip them" | Deploying untested code is how you get paged at 3 AM. Run the tests. |
| "It works on my machine" | That is not evidence. The test suite is evidence. |
| "I'll just deploy and fix issues as they come" | You have no rollback plan if you don't know what changed. Check the diff first. |