Pre-deploy check skill: is it ready to ship?

An agent skill that runs build, tests and lint, checks secrets, env vars and database access, then answers READY, READY WITH WARNINGS or BLOCKED.

· By Codema Editorial

Free account required

It reports first and fixes nothing unless you ask. Dashboard checks are marked NEEDS HUMAN.

Preview: SKILL.md

# Pre-deploy check

Run these steps in order. Do not fix anything unless the user asks; report first.

## 1. Build and tests

- Find the project's build, test and lint commands in `package.json` scripts, `AGENTS.md` or the README. Do not invent commands.
- Run each one. Record the command, pass or fail, and the key lines of any failure.

## 2. Secrets

- Search the diff against the main branch for hard-coded keys, tokens, passwords or connection strings.
- Flag any secret-looking value that is not read from an environment variable.
- Flag any server-only secret referenced with a public prefix (for example `NEXT_PUBLIC_`).
- Check `.gitignore` covers `.env` and `.env*.local`, and that no such file is tracked (`git ls-files | grep -i '\.env'`). `.env.example` with names only is fine.

What's inside

  • One validated SKILL.md
  • Six steps: build and tests, secrets, env vars, database access, production basics, report

How to use it

  1. Unzip into your skills folder.
  2. Ask: "is this ready to ship?"
  3. Fix every FAIL. Read every WARN.

Who it's for

Anyone who deploys straight from an agent session.

Keep reading

Keep reading

Newsletter

The Codema publication. Consent is required. You are not subscribed until you confirm from the email, and nothing is stored if email delivery is not connected.