agentleFS
Sign inStart free
shuvamkshuvamk/openbench/.claude/skills/deploy-sanity/SKILL.md

deploy-sanity

Skill2 starsChanged 5 months agoApache-2.0View on GitHub

After a Vercel production deploy, verify the live URL renders and core routes respond; append .context/deploy-log.md. On failure, open a p0 bug and revert main to last good. Run after every production deploy.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never leave production red while investigating.

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

deploy-sanity

main merges auto-deploy to production, and the human's only feedback loop is the live site — so every deploy gets verified, and failures roll back immediately.

Procedure

  1. Get the production URL (Vercel project openbench; also in the repo variable OPENBENCH_PROD_URL).
  2. Probe:
    • GET / → 200, body contains "OpenBench" (marker check, not just status).
    • GET /api/health → 200 JSON { ok: true, irVersion }.
    • Editor route /editor (or current entry route) → 200.
  3. Healthy → append one row to .context/deploy-log.md: | <UTC date> | <short sha> | <one-line what changed> | <risk notes or —> | and commit it with the next PR (or directly if branch protection allows admin).
  4. Unhealthy → a. gh issue create --label "type:bug,area:agent-ops,status:ready,p0" --title "p0: production unhealthy after <sha>" with probe output in the body. b. Revert: branch revert/deploy-<sha8>, git revert <bad sha>, push, PR titled revert: unhealthy production deploy (<sha>) — auto-merge lands it once green. c. Append the failure + revert to deploy-log.md.
  5. Never leave production red while investigating. Revert first, diagnose second.

CI runs the same probe automatically (deploy-sanity.yml) on every push to main; this skill is the richer in-session version (multi-route, log-writing).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free