agentleFS
LeostrukaLeostruka/devin-bundle/skills/deploy/SKILL.md

deploy

Skill0 starsChanged 3 months agoMITView on GitHub

Use when the user wants to release, deploy, rollback, or verify a deployment pipeline. Covers CI/CD gates, environment checks, canary/blue-green, and post-deploy smoke tests.

155 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pm-discovery, qa-phase and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ww-w-aiSkill

    pm-discovery

    PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase.

    Also in 3 projects that use this

  • ww-w-aiSkill

    qa-phase

    Run QA tests at various levels (L1-L5) for features under PDCA management. Integrates with MCP tools to execute structured test plans.

    Also in 3 projects that use this

  • +10 more from ww-w-ai

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 139 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Confirm artifact: Verify that the build/test/lint gates passed before deploy.

    line 20
  2. Distinctive:

    Check environment: Read deployment config, secrets, and target infrastructure.

    line 21
  3. Very specific:

    Execute deploy: Use the project's deployment command (e.g., npm run deploy, docker compose up, kubectl apply, gh workflow run).

    line 23
  4. Distinctive:

    After deploy, run smoke tests and report: URL, version, status, rollback command.

    line 34
  5. Distinctive:

    If rollback is needed, run it and verify the previous version is healthy.

    line 35

“Common” is measured: kept by at least 6 in 10 of the 139 edited versions of this file we could read. “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

Deploy, release, and verify code in target environments.

When to use

  • User asks to deploy, release, or promote to staging/production.
  • Rollback is needed.
  • Post-deploy smoke tests or health checks are required.
  • Need to choose between canary, blue-green, or simple rollout.

Core protocol

  1. Confirm artifact. Verify that the build/test/lint gates passed before deploy.
  2. Check environment. Read deployment config, secrets, and target infrastructure.
  3. Choose strategy. Canary, blue-green, rolling, or all-at-once based on risk.
  4. Execute deploy. Use the project's deployment command (e.g., npm run deploy, docker compose up, kubectl apply, gh workflow run).
  5. Run smoke tests. Hit health endpoints, run critical e2e checks.
  6. Verify and report. Confirm success or trigger rollback.

See also

  • docker — container build, run, and compose.
  • deploy — release orchestration, rollback, and smoke tests.

Output rule

  • After deploy, run smoke tests and report: URL, version, status, rollback command.
  • If rollback is needed, run it and verify the previous version is healthy.

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.