Agent skill

Deployment Strategies

Deployment strategy catalog. An agent skill from revfactory/harness-100.

Apache-2.0Auto-check passedDevOps & Cloud

Install Deployment Strategies

skills CLI

$ npx skills add revfactory/harness-100 --skill deployment-strategies -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install revfactory/harness-100 deployment-strategies --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .claude/skills && cp -r skills-src/en/20-cicd-pipeline/.claude/skills/deployment-strategies .claude/skills/deployment-strategies && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "deployment-strategies" agent skill from https://github.com/revfactory/harness-100/tree/main/en/20-cicd-pipeline/.claude/skills/deployment-strategies into .claude/skills/deployment-strategies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deployment-strategies", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/revfactory/harness-100/tree/main/en/20-cicd-pipeline/.claude/skills/deployment-strategies

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add revfactory/harness-100 --skill deployment-strategies -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install revfactory/harness-100 deployment-strategies --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .agents/skills && cp -r skills-src/en/20-cicd-pipeline/.claude/skills/deployment-strategies .agents/skills/deployment-strategies && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "deployment-strategies" agent skill from https://github.com/revfactory/harness-100/tree/main/en/20-cicd-pipeline/.claude/skills/deployment-strategies into .agents/skills/deployment-strategies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deployment-strategies", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add revfactory/harness-100 --skill deployment-strategies -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install revfactory/harness-100 deployment-strategies --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/en/20-cicd-pipeline/.claude/skills/deployment-strategies .cursor/skills/deployment-strategies && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "deployment-strategies" agent skill from https://github.com/revfactory/harness-100/tree/main/en/20-cicd-pipeline/.claude/skills/deployment-strategies into .cursor/skills/deployment-strategies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deployment-strategies", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/revfactory/harness-100.git --path en/20-cicd-pipeline/.claude/skills/deployment-strategies

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add revfactory/harness-100 --skill deployment-strategies -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install revfactory/harness-100 deployment-strategies --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/en/20-cicd-pipeline/.claude/skills/deployment-strategies .gemini/skills/deployment-strategies && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "deployment-strategies" agent skill from https://github.com/revfactory/harness-100/tree/main/en/20-cicd-pipeline/.claude/skills/deployment-strategies into .gemini/skills/deployment-strategies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deployment-strategies", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install revfactory/harness-100 deployment-strategies

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add revfactory/harness-100 --skill deployment-strategies -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .github/skills && cp -r skills-src/en/20-cicd-pipeline/.claude/skills/deployment-strategies .github/skills/deployment-strategies && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "deployment-strategies" agent skill from https://github.com/revfactory/harness-100/tree/main/en/20-cicd-pipeline/.claude/skills/deployment-strategies into .github/skills/deployment-strategies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deployment-strategies", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add revfactory/harness-100 --skill deployment-strategies -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install revfactory/harness-100 deployment-strategies --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/en/20-cicd-pipeline/.claude/skills/deployment-strategies .opencode/skills/deployment-strategies && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "deployment-strategies" agent skill from https://github.com/revfactory/harness-100/tree/main/en/20-cicd-pipeline/.claude/skills/deployment-strategies into .opencode/skills/deployment-strategies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deployment-strategies", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: deployment-strategies
GitHub stars: 1.3k
Token cost: ~1.7k tokens
SKILL.md length: 467 words
Files: 1
Skills in repo: 464
Repo updated: Mar 22, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Deployment strategy catalog. An agent skill from revfactory/harness-100.

Works in 5 steps: Rolling Update (Sequential Replacement) → Blue-Green Deployment → Canary Deployment → …
Designing deployment pipelines involving deployment strategy
SKILL.md covers Target Agent, Deployment Strategy Comparison, Strategy Details and Health Check Design, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Deployment Strategies is an agent skill from revfactory/harness-100. Deployment strategy catalog. An extension skill for pipeline-designer that provides pros/cons, implementation patterns, rollback procedures, health check design, and DORA metrics for Blue-Green/Canary/Rolling/A-B Test/Shadow deployment strategies. Use when designing deployment pipelines involving 'deployment strategy', 'Blue-Green', 'Canary', 'Rolling', 'rollback', 'zero-downtime deployment', 'DORA metrics', etc. Note: actual infrastructure configuration and monitoring tool setup are outside the scope of this…

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Deployment. The licence is Apache-2.0.

When your agent uses it

Designing deployment pipelines involving deployment strategy
Zero-downtime deployment

Example prompts

“deployment strategy”
“Blue-Green”
“Canary”
“/deployment-strategies”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Rolling Update (Sequential Replacement)
Blue-Green Deployment
Canary Deployment
A/B Testing (Feature Experiment)
Shadow (Mirroring)

What it can do on your machine

Read from SKILL.md and the folder at commit 8e8d35c. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml and json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Deployment Strategies loads about 1.7k tokens when it runs. Until then it costs about 136 tokens; SKILL.md has 467 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~136
When it runs · the whole SKILL.md, loaded when a task matches: ~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from revfactory/harness-100 at commit 8e8d35c, republished under its Apache-2.0 licence (© revfactory). 467 words, ~1,735 tokens.

Download SKILL.mdSave it as .claude/skills/deployment-strategies/SKILL.md (or your agent's skills folder).

name: deployment-strategies
description: Deployment strategy catalog. An extension skill for pipeline-designer that provides pros/cons, implementation patterns, rollback procedures, health check design, and DORA metrics for Blue-Green/Canary/Rolling/A-B Test/Shadow deployment strategies. Use when designing deployment pipelines involving 'deployment strategy', 'Blue-Green', 'Canary', 'Rolling', 'rollback', 'zero-downtime deployment', 'DORA metrics', etc. Note: actual infrastructure configuration and monitoring tool setup are outside the scope of this skill.

Deployment Strategies — Deployment Strategy Catalog

A reference of deployment strategies, rollback procedures, health checks, and DORA metrics used by the pipeline-designer agent when designing deployment pipelines.

Target Agent

pipeline-designer — Directly applies the deployment strategies and rollback patterns from this skill to pipeline design.

Deployment Strategy Comparison

Strategy	Downtime	Risk	Infra Cost	Rollback Speed	Best For
Rolling	None	Medium	Low	Medium	General web services
Blue-Green	None	Low	2x	Instant	Mission-critical
Canary	None	Very low	Slightly extra	Instant	High-traffic systems
Recreate	Yes	High	None	Slow	Dev/staging
A/B Test	None	Low	Slightly extra	Instant	Feature experiments
Shadow	None	None	2x	N/A	Performance/compatibility validation

Strategy Details

1. Rolling Update (Sequential Replacement)

Server pool: [v1] [v1] [v1] [v1]
Step 1:      [v2] [v1] [v1] [v1]  -- 1 replaced
Step 2:      [v2] [v2] [v1] [v1]  -- 2 replaced
Step 3:      [v2] [v2] [v2] [v1]  -- 3 replaced
Step 4:      [v2] [v2] [v2] [v2]  -- Complete

Configuration parameters:

maxUnavailable: Maximum instances to take down simultaneously (1 or 25%)
maxSurge: Maximum instances to add simultaneously (1 or 25%)

Kubernetes example:

yaml

strategy:
  type: RollingUpdate
  rollingUpdate:
    maxUnavailable: 1
    maxSurge: 1

Pros: Minimal extra infrastructure, gradual replacement Cons: v1+v2 coexistence period (requires compatibility)

2. Blue-Green Deployment

Blue (current):  [v1] [v1] [v1]  <- 100% traffic
Green (standby): [v2] [v2] [v2]  <- 0% traffic

Switch:
Blue:   [v1] [v1] [v1]  <- 0% traffic (standby/remove)
Green:  [v2] [v2] [v2]  <- 100% traffic

Procedure:

Deploy new version to Green environment
Run smoke tests/health checks on Green
Switch load balancer traffic to Green
Monitor Blue environment (rollback standby)
After stabilization, remove Blue or hold for next deployment

Rollback: Re-switch load balancer to Blue (within seconds)

3. Canary Deployment

Step 1: [v1 x 95%] [v2 x 5%]   -- Start with 5% traffic
Step 2: [v1 x 80%] [v2 x 20%]  -- Expand if metrics are normal
Step 3: [v1 x 50%] [v2 x 50%]  -- Further expansion
Step 4: [v2 x 100%]             -- Full rollout

Per-stage validation criteria:

Stage	Traffic	Wait Time	Validation
1	5%	10-30 min	Error rate, latency
2	20%	30-60 min	Add business metrics
3	50%	1-2 hours	All metrics
4	100%	-	Complete

Automatic rollback conditions:

Error rate > 1% (2x normal)
p99 latency > 2 seconds (50% increase from normal)
Business metric anomaly (conversion rate, revenue, etc.)

4. A/B Testing (Feature Experiment)

Traffic splitting based on user segments
Integrated with Feature Flag systems
Decide after achieving statistical significance

5. Shadow (Mirroring)

Replicate production traffic to new version (responses discarded)
Used only for performance, error, and compatibility validation
Zero user impact

Show full SKILL.md (176 more words)Show less

Health Check Design

Three-Level Health Checks

Type	Validates	Endpoint	Interval
Liveness	Process survival	`/healthz`	10s
Readiness	Ready to receive traffic	`/readyz`	5s
Startup	Initialization complete	`/healthz`	1s (max 300s)

Health Check Response Structure

json

{
  "status": "healthy",
  "version": "2.1.0",
  "uptime": 86400,
  "checks": {
    "database": { "status": "healthy", "latency": "2ms" },
    "redis": { "status": "healthy", "latency": "1ms" },
    "external_api": { "status": "degraded", "latency": "500ms" }
  }
}

Kubernetes Probe Configuration

yaml

livenessProbe:
  httpGet:
    path: /healthz
    port: 8080
  initialDelaySeconds: 15
  periodSeconds: 10
  failureThreshold: 3

readinessProbe:
  httpGet:
    path: /readyz
    port: 8080
  initialDelaySeconds: 5
  periodSeconds: 5
  failureThreshold: 3

Rollback Procedures

Automatic Rollback Triggers

Metric	Threshold	Duration
HTTP 5xx rate	> 5%	2 min consecutive
Latency p99	> 3s	5 min consecutive
Pod restarts	> 3 times	Within 10 min
Memory/CPU	> 90%	5 min consecutive

Rollback Procedure

1. Trigger detected -> Auto-alert (Slack/PagerDuty)
2. Immediate switch to previous version
   - Blue-Green: Switch load balancer
   - Canary: Set canary traffic to 0%
   - Rolling: kubectl rollout undo
3. Root Cause Analysis (RCA)
4. Fix and redeploy

DORA Metrics

4 Key Metrics

Metric	Description	Elite	High	Medium	Low
Deployment frequency	Production deployment cadence	On demand (multiple/day)	Daily-weekly	Monthly	Less than monthly
Lead time	Commit-to-deploy time	< 1 hour	1 day-1 week	1 week-1 month	1 month+
Change failure rate	Post-deployment failure ratio	< 5%	6-15%	16-30%	> 30%
Recovery time	Incident-to-recovery time	< 1 hour	< 1 day	1 day-1 week	1 week+

Measurement Automation

Deployment frequency = Production deployment event count / period
Lead time = Production deploy time - First commit time
Change failure rate = Rollback deployments / Total deployments x 100
Recovery time = Incident resolution time - Incident detection time

Branch Strategy and Deployment Mapping

Branch Strategy	Deployment Flow	Best For
Trunk-Based	main -> staging -> production	Small teams, frequent deployments
GitHub Flow	feature -> PR -> main -> production	Medium teams, mature CI/CD
GitFlow	feature -> develop -> release -> main	Large teams, fixed release cycles

Per-Environment Auto-Deployment Rules

feature/* -> PR -> preview environment (ephemeral)
main       -> auto -> staging (automated testing)
main + tag -> manual approval -> production
hotfix/*   -> emergency -> production (simplified approval)

Files

Just SKILL.md in en/20-cicd-pipeline/.claude/skills/deployment-strategies of revfactory/harness-100.

Open the folder on GitHubat commit 8e8d35c

Compare with similar skills

Deployment Strategies next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Deployment Strategies compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Deployment Strategies this skillrevfactory/harness-100	1.3k	—	~1.7k	Automated safety check: Pass	Apache-2.0	6 mo ago
Kubeshark Installerkubeshark/kubeshark	12k	—	~3.6k	Automated safety check: Notes	Apache-2.0	2 days ago
GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb	6.7k	—	~4k	Automated safety check: Notes	Apache-2.0	today
KubeSphere ServiceMesh Managerkubesphere/kubesphere	17k	—	~2.4k	Automated safety check: Pass	Custom licence	2 mo ago
Vercelremotion-dev/remotion	63k	—	~1.2k	Automated safety check: Pass	Custom licence	today
AWS Cdk Developmentzxkane/aws-skills	367	2 repos	~2.5k	Automated safety check: Pass	MIT	3 mo ago

Similar skills

Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
12k GitHub stars~3.6k tokensUpdated 2 days ago
DevOps & CloudAuto-check: notes
GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
6.7k GitHub stars~4k tokensUpdated today
DevOps & CloudAuto-check: notes
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
17k GitHub stars~2.4k tokensUpdated 2 mo ago
DevOps & CloudAuto-check passed
Vercel
remotion-dev/remotion
Official
Set up a Codex monitor for Vercel deployments and preview URLs.
63k GitHub stars~1.2k tokensUpdated today
DevOps & CloudAuto-check passed
AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
367 GitHub starsUsed in 2 repos~2.5k tokens
DevOps & CloudAuto-check passed
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
260 GitHub starsUsed in 6 repos~1.1k tokens
DevOps & CloudAuto-check: notes

Questions about Deployment Strategies

What does Deployment Strategies do?

Deployment strategy catalog. An agent skill from revfactory/harness-100. Deployment Strategies is an agent skill from revfactory/harness-100. Deployment strategy catalog.

When should I use Deployment Strategies?

Deployment Strategies fits situations like: designing deployment pipelines involving deployment strategy; zero-downtime deployment.

How do I install Deployment Strategies in Claude Code?

Run `npx skills add revfactory/harness-100 --skill deployment-strategies -a claude-code`. Or copy the skill folder (en/20-cicd-pipeline/.claude/skills/deployment-strategies in revfactory/harness-100) into .claude/skills/deployment-strategies in your project. Claude Code loads it when a task matches its description.

How do I install Deployment Strategies in Codex?

Run `npx skills add revfactory/harness-100 --skill deployment-strategies -a codex`. Or copy the skill folder (en/20-cicd-pipeline/.claude/skills/deployment-strategies in revfactory/harness-100) into .agents/skills/deployment-strategies in your project. Codex loads it when a task matches its description.

Can I use Deployment Strategies in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add revfactory/harness-100 --skill deployment-strategies -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deployment-strategies, .gemini/skills/deployment-strategies, .github/skills/deployment-strategies and .opencode/skills/deployment-strategies in your project.

What does Deployment Strategies need to run?

SKILL.md names no scripts, command-line tools or credentials: Deployment Strategies is instructions for the agent only.

Does Deployment Strategies access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Deployment Strategies safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Deployment Strategies use?

Deployment Strategies is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Deployment Strategies use?

About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Deployment Strategies?

Skills that share tags, products or a category with Deployment Strategies: Kubeshark Installer (kubeshark/kubeshark, 12k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars) and Vercel (remotion-dev/remotion, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Deployment Strategies?

revfactory (a GitHub user) maintains it in revfactory/harness-100, which has 1,295 GitHub stars. The repository holds 464 skills in this directory. The repository was last updated on March 22, 2026.

Source: revfactory/harness-100 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Deployment Strategies

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Deployment Strategies — Deployment Strategy Catalog

Target Agent

Deployment Strategy Comparison

Strategy Details

1. Rolling Update (Sequential Replacement)

2. Blue-Green Deployment

3. Canary Deployment

4. A/B Testing (Feature Experiment)

5. Shadow (Mirroring)

Health Check Design

Three-Level Health Checks

Health Check Response Structure

Kubernetes Probe Configuration

Rollback Procedures

Automatic Rollback Triggers

Rollback Procedure

DORA Metrics

4 Key Metrics

Measurement Automation

Branch Strategy and Deployment Mapping

Per-Environment Auto-Deployment Rules

Files

Compare with similar skills

Similar skills

More from revfactory/harness-100

Related

Questions about Deployment Strategies