agentleFS
Sign inStart free
VoTruongDanhVoTruongDanh/Skills-Agent/.cursor/skills/deploy/SKILL.md

deploy

Skill4 starsChanged 33 days agoMITView on GitHub

Deployment steps, release preparation, environment setup, CI/CD guidance, and production rollout. Use when the user wants to deploy, release, or set up infrastructure. Triggers: deploy, release, CI/CD, docker, production, triển khai, phát hành, đưa lên production.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 138 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    START: Read .ai-memory.md from project root.

    line 10
  2. Very specific:

    END: Update .ai-memory.md using Memory Compaction Rules with: target, steps, env details, issues, rollback notes, and infra decisions.

    line 11
  3. Distinctive:

    If any answer is unclear, ASK before proceeding.

    line 27
  4. Distinctive:

    Call out risky steps explicitly.

    line 34
  5. Distinctive:

    Prefer least-risk rollout patterns.

    line 61
  6. Distinctive:

    Avoid unrelated infra/app changes.

    line 64
  7. Distinctive:

    Always read and update the memory file.

    line 65
  8. Very specific:

    All code snippets and example files referenced or produced by this skill must be UTF-8 encoded.

    line 73

“Common” is measured: kept by at least 6 in 10 of the 138 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

Memory Protocol

START: Read .ai-memory.md from project root. Check deployment history, target environments, known infrastructure, CI/CD setup, past deployment issues. END: Update .ai-memory.md using Memory Compaction Rules with: target, steps, env details, issues, rollback notes, and infra decisions.

Goal

Prepare a safe, repeatable deployment or release plan.

Agent Routing

  • For infrastructure/CI/CD → read .kiro/skills/agents/agents/devops-engineer.md and apply its knowledge
  • For security review before deploy → read .kiro/skills/agents/agents/security-auditor.md and apply its knowledge
  • For database migrations → read .kiro/skills/agents/agents/database-architect.md and apply its knowledge
  • For performance validation → read .kiro/skills/agents/agents/performance-optimizer.md and apply its knowledge

Socratic Gate

Before deploying, verify:

  1. What is the target environment? (staging, production, preview?)
  2. Are all tests passing?
  3. Are there database migrations or breaking changes? If any answer is unclear, ASK before proceeding.

Workflow

  1. Read Memory — Load .ai-memory.md for deployment history and environment details.
  2. Detect the app type, runtime, dependencies, and target environment.
  3. List prerequisites: secrets, env vars, build steps, infrastructure, database migrations, and health checks.
  4. Produce a deployment sequence from pre-checks to rollback.
  5. Call out risky steps explicitly.
  6. Include post-deploy verification and monitoring.
  7. Quality Gate — Read .kiro/skills/_scripts/pre-deploy.md for pre-deploy checklist, then .kiro/skills/_scripts/checklist.md for cross-cutting checks.
  8. Update Memory — Save deployment details and outcomes to .ai-memory.md.

Output format

  • Target environment
  • Preconditions
  • Deployment steps (numbered, with risk flags)
  • Verification (health checks, smoke tests)
  • Rollback plan

Checklist

  • Target environment confirmed
  • All tests passing
  • Secrets/env vars configured
  • Database migrations planned
  • Build artifacts ready
  • Rollback plan documented
  • Health checks defined
  • Post-deploy verification planned
  • Memory file updated
  • Clean code chuẩn (Standard clean code applied)
  • Cập nhật đầy đủ tất cả các file liên quan (All related files fully updated)

Rules

  • Prefer least-risk rollout patterns.
  • Never expose secrets.
  • Distinguish clearly between required and optional steps.
  • Avoid unrelated infra/app changes; if a deployment step requires broad refactors, ASK first.
  • Always read and update the memory file.

Related Skills

  • /test → read .kiro/skills/test/SKILL.md — Run tests before deployment
  • /status → read .kiro/skills/status/SKILL.md — Check project readiness
  • /plan → read .kiro/skills/plan/SKILL.md — Plan complex deployment sequences

Encoding

All code snippets and example files referenced or produced by this skill must be UTF-8 encoded. When applicable, include encoding: "UTF-8" in SKILL.md front-matter and ensure saved files use UTF-8 (no BOM).

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