agentleFS
AsiaOstrichAsiaOstrich/EngramGraph/.agents/skills/deploy-assistant/SKILL.md

deploy

Skill4 starsChanged 28 days agoMITView on GitHub

Guide reliable deployments without CI/CD platforms (GitHub Actions / GitLab CI). Use when: deploying to VPS, air-gapped servers, or environments without CI/CD infrastructure. Not for: pipelines on GitHub Actions or GitLab CI — use /ci-cd; version bumps and release promotion — use /release. Keywords: deployment, no-cicd, shell script, blue-green, smoke test, rollback.

  • Commits and pushes

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

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 139 edited versions we read keep these.

  • 1

    Distinctive

    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:

    After generation, AI assistant must confirm:

    line 143
  2. Very specific:

    After /deploy completes, the AI assistant should suggest:

    line 162

“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

No-CI/CD Deploy Assistant | 無 CI/CD 部署助手

Language: English | 繁體中文

Guide reliable deployments in environments without GitHub Actions or GitLab CI, using a three-layer architecture: prevent errors, verify correctness, recover fast.

引導無 CI/CD 平台環境下的可靠部署,採用三層架構:防錯、驗證、快速回復。

Three-Layer Architecture | 三層部署架構

Layer 1: Prevent Wrong Deployments   Layer 2: Verify Correctness   Layer 3: Fast Recovery
  set -euo pipefail                    Smoke Test + /health           Blue-Green switching
  Version tag enforcement              Version number comparison      rollback.sh < 30s
  deploy.lock concurrency guard        Auto-rollback on failure

Interactive Questionnaire | 引導式問答

QuestionOptionsImpact
Project typenode / python / go / dockerBuild command
Deploy targetSSH+rsync / Docker ComposeTransfer method
Blue-Green supportyes / norollback.sh generation
Health check URLURL inputverify.sh target
Version sourceVERSION file / package.json / git tagVersion comparison logic

Generated Script Set | 生成的腳本組

deploy.sh — Main Deploy Script

#!/usr/bin/env bash
set -euo pipefail

LOCK_FILE="/tmp/deploy.lock"
trap "rm -f $LOCK_FILE" EXIT

# Concurrency guard | 防並發
if [ -f "$LOCK_FILE" ]; then
  echo "❌ Deploy in progress (PID: $(cat $LOCK_FILE))"
  exit 1
fi
echo $$ > "$LOCK_FILE"

# Version tag enforcement | 版本 tag 強制
CURRENT_TAG=$(git describe --exact-match --tags HEAD 2>/dev/null || echo "")
if [ -z "$CURRENT_TAG" ]; then
  echo "❌ No version tag on HEAD. Run: git tag vX.Y.Z && git push --tags"
  exit 1
fi

echo "[1/4] Running tests..."
# {TEST_COMMAND}

echo "[2/4] Building artifact..."
# {BUILD_COMMAND}

echo "[3/4] Syncing to server..."
rsync -avz --delete ./dist/ {USER}@{SERVER}:/app/

echo "[4/4] Verifying deployment..."
./verify.sh || { echo "Verification failed, rolling back..."; ./rollback.sh; exit 1; }

echo "{\"timestamp\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\",\"version\":\"$CURRENT_TAG\",\"operator\":\"$(whoami)\",\"result\":\"success\"}" >> /var/log/deployments.jsonl
echo "✅ Deploy successful: $CURRENT_TAG"

verify.sh — Smoke Test

#!/usr/bin/env bash
set -euo pipefail

HEALTH_URL="${HEALTH_URL:-{HEALTH_URL}}"
EXPECTED_VERSION=$(cat VERSION)

for i in $(seq 1 3); do
  RESPONSE=$(curl -sf --max-time 10 "$HEALTH_URL" 2>/dev/null) && break
  echo "Health check attempt $i/3 failed, retrying in 5s..."
  sleep 5
done

ACTUAL_VERSION=$(echo "$RESPONSE" | python3 -c "import json,sys; print(json.load(sys.stdin)['version'])")

if [ "$ACTUAL_VERSION" != "$EXPECTED_VERSION" ]; then
  echo "❌ Version mismatch! Expected $EXPECTED_VERSION, got $ACTUAL_VERSION"
  exit 1
fi

echo "✅ Version verified: $ACTUAL_VERSION"

rollback.sh — Blue-Green Rollback

#!/usr/bin/env bash
set -euo pipefail

CURRENT=$(readlink /app/current 2>/dev/null || echo "/app/blue")
TARGET=$([[ "$CURRENT" == *"green"* ]] && echo "/app/blue" || echo "/app/green")

ln -sfn "$TARGET" /app/current
nginx -s reload

echo "✅ Rolled back to $TARGET ($(date -u +%Y-%m-%dT%H:%M:%SZ))"
echo "{\"timestamp\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\",\"event\":\"rollback\",\"from\":\"$CURRENT\",\"to\":\"$TARGET\",\"operator\":\"$(whoami)\"}" >> /var/log/deployments.jsonl

Makefile

.PHONY: deploy rollback verify status

deploy:
	@./deploy.sh

rollback:
	@./rollback.sh

verify:
	@./verify.sh

status:
	@echo "Current slot: $$(readlink /app/current 2>/dev/null || echo 'N/A')"
	@curl -s $${HEALTH_URL:-http://localhost/health} | python3 -m json.tool 2>/dev/null || echo "Health check failed"

Output Checklist | 輸出確認清單

After generation, AI assistant must confirm:

  • deploy.sh includes set -euo pipefail
  • deploy.sh includes deploy.lock concurrency guard
  • verify.sh compares version number (not just HTTP 200)
  • rollback.sh triggers automatically on verify failure
  • Makefile provides make deploy / make rollback / make status

Usage | 使用方式

/deploy              # Interactive mode — auto-detect project type
/deploy node         # Node.js project, generate directly
/deploy docker       # Docker Compose deploy mode
/deploy --verify-only  # Generate verify.sh only

Next Steps Guidance | 下一步引導

After /deploy completes, the AI assistant should suggest:

Deploy scripts generated. Suggested next steps / 部署腳本已生成,建議下一步:

  • chmod +x deploy.sh verify.sh rollback.sh — Set executable permissions | 設定執行權限
  • make verify — Test health check configuration | 測試健康檢查設定
  • git tag v1.0.0 && git push --tags — Create version tag | 建立版本 tag
  • make deploy — First deployment | 執行第一次部署

Reference | 參考

  • Core standard: no-cicd-deployment.md
  • Core standard: deployment-standards.md
  • Core standard: deployment-standards.md § Defensive Deployment Ordering — MANDATORY extract-verify-then-delete sequence for destructive updates / 強制遵循 extract-verify-then-delete 順序
  • Core standard: packaging-standards.md § Archive Format Integrity — verify archive format before consuming / 消費 archive 前先驗證格式
  • Related: ci-cd-assistant — For environments WITH CI/CD

Version History | 版本歷史

VersionDateChanges變更說明
1.0.02026-04-26Initial release — XSPEC-085 Phase 1b初始版本

License | 授權

CC BY 4.0 — Documentation content

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.