Continuous Delivery

Apply Jez Humble and David Farley's Continuous Delivery — the discipline of making software always release-ready through deployment pipelines, trunk-based development, automated everything, feature flags, branch-by-abstraction, and the four DORA metrics (deployment frequency, lead time, change failure rate, mean time to restore). Use when designing a deployment pipeline, choosing a branching strategy, debating long-lived feature branches vs. trunk-based, deciding how to deploy in-flight changes safely, or evaluating delivery health.

5 stars 2 forksGit & Code Review Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add vnovakovits/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add vnovakovits/claude-skills --skill continuous-delivery
Manual install
git clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/continuous-delivery ~/.claude/skills/continuous-delivery

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Continuous Delivery (Humble & Farley)

Apply this skill when designing or improving how software gets from commit to production — pipelines, branching, deployment strategies, feature flags, release planning, and the metrics that distinguish high-performing from low-performing engineering organizations.

## Core Philosophy

**Done means released.** Not "feature-complete on a branch", not "merged to main", not "deployed to staging". Done means in production, available to users (or hideable behind a flag).

**Software is always release-ready.** Every commit, every branch, every build — the trunk is always in a deployable state. Releasing becomes a business decision, not a technical event.

**If it hurts, do it more often.** Painful integrations? Integrate continuously. Painful deployments? Deploy continuously. The pain reveals problems; doing it more often forces you to automate and improve the painful parts.

**Build quality in.** Quality is not inspected at the end. It is a property of the process: tests at every stage, automated checks, fast feedback, and a build that breaks loudly when something is wrong.

**Optimize for low MTTR over high MTBF.** Mean Time To Recovery matters more than Mean Time Between Failures. A team that recovers in minutes can move fast; a team that goes weeks without an incident but takes days to recover when one happens cannot.

---

## The Deployment Pipeline
Read the full skill on GitHub

Details

Skill name
continuous-delivery
Path
plugins/engineering-practices/skills/continuous-delivery/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the Continuous Delivery skill do?

Apply Jez Humble and David Farley's Continuous Delivery — the discipline of making software always release-ready through deployment pipelines, trunk-based development, automated everything, feature flags, branch-by-abstraction, and the four DORA metrics (deployment frequency, lead time, change failure rate, mean time to restore). Use when designing a deployment pipeline, choosing a branching strategy, debating long-lived feature branches vs. trunk-based, deciding how to deploy in-flight changes safely, or evaluating delivery health.

How do I install the Continuous Delivery skill?

Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Continuous Delivery popular?

It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.

Related skills

Accidental Cio

5

vnovakovits/claude-skills

Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to

Frontend & Design

Agent Retro

5

vnovakovits/claude-skills

Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee

AI, LLMs & Agents

API Design

5

vnovakovits/claude-skills

Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.

Software Development

File Validation

8

Freddy-CHEN-ux/00_claude_skills

Strict detection and removal of unrelated files before PR creation

Git & Code Review

Branch Discipline

8

Freddy-CHEN-ux/00_claude_skills

Enforce one branch per issue, small focused commits, and clean git history. Use with /branch command.

Git & Code Review

Finishing a Development Branch

8

Freddy-CHEN-ux/00_claude_skills

Use when ready to merge feature branch. Complete checklist before creating PR/MR. Ensures professional quality and prevents embarrassing mistakes.

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.