agentleFS
Sign inStart free
HarambeeAIHarambeeAI/bayes-ship/skills/ship-deploy/SKILL.md

ship-deploy

Skill1 starsChanged 7 months agoMITView on GitHub

Deploy the product to production. Runs deployment checklist, executes deploy commands, verifies health post-deployment. Supports Railway and Vercel.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read ARCHITECTURE.md for deployment targets.

    line 10
  2. Distinctive:

    Check for missing environment variables.

    line 18
  3. Distinctive:

    Verify key user flows work in production

    line 25
  4. Very specific:

    Update progress.json with deployment status and URLs.

    line 27
  5. Distinctive:

    Never deploy without passing tests.

    line 31
  6. Distinctive:

    Never deploy with critical security findings unresolved.

    line 32
  7. Distinctive:

    Always verify post-deployment.

    line 33

≈ “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 — Production deployment

Process

  1. Read ARCHITECTURE.md for deployment targets.
  2. Run deployment checklist:
    • On main branch (or approved branch)?
    • Environment variables configured?
    • Database migrations ready?
    • Build passing?
    • Full test suite passing?
    • Security scan clean?
  3. Check for missing environment variables. If any are missing, prompt the user for each one. Offer to generate secrets (like auth keys) where appropriate.
  4. Execute deployment:
    • Backend → Railway (or configured provider)
    • Frontend → Vercel (or configured provider)
    • Database → Run migrations
  5. Post-deployment verification:
    • Hit health check endpoints
    • Verify key user flows work in production
    • Report deployment URLs
  6. Update progress.json with deployment status and URLs.

Rules

  • Never deploy without passing tests.
  • Never deploy with critical security findings unresolved.
  • Always verify post-deployment. A deployment without health check is incomplete.

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