One-click install
npx skills add https://github.com/syntropic137/harness-app-template --skill continuous-delivery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: continuous-delivery
Source: https://github.com/syntropic137/harness-app-template/tree/main/.claude/skills/continuous-delivery
Command: npx skills add https://github.com/syntropic137/harness-app-template --skill continuous-delivery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering teams often struggle with slow, risky, and unmeasured delivery pipelines that lead to frequent incidents, long lead times, and wasted effort on manual release processes, with no clear way to track or improve delivery performance over time.

Core Features & Use Cases

  • DORA Metrics Alignment: Measure and improve the four key delivery metrics (lead time, deployment frequency, change failure rate, mean time to restore) to drive data-backed performance gains.
  • End-to-End Pipeline Guardrails: Enforce pre-merge gating, trunk-based development, build-once-promote artifact flow, and health-gated deploys to reduce release risk and eliminate environment drift.
  • Use Case: A team shipping a customer-facing web service can use this skill to audit their CI/CD setup, implement automated rollback, and decouple deploys from releases via feature flags to cut change failure rate by 30% in one quarter.

Quick Start

Use the continuous-delivery skill to audit your current CI/CD pipeline against DORA metrics and identify the top 3 highest-impact improvements to implement this sprint.

Frequently Asked Questions about continuous-delivery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I measure CI/CD pipeline performance using DORA metrics?

DORA metrics measure delivery performance by tracking lead time, deployment frequency, change failure rate, and mean time to restore. You can audit your CI/CD pipeline against these four key metrics to identify high-impact improvements and drive data-backed performance gains.

What is the best way to implement health-gated deploys and automated rollback?

Health-gated deploys reduce release risk by enforcing automated guardrails before promoting artifacts. You can implement exercised automated rollback procedures and health-gated deployment systems to cut change failure rate and ensure safe production releases.

How does build-once-promote artifact flow improve trunk-based development?

Build-once-promote artifact flow eliminates environment drift by promoting a single artifact through pipeline stages. Combined with trunk-based development and pre-merge gating, it enforces pipeline guardrails and ensures environment consistency across continuous delivery workflows.

Can I enforce pre-merge gating and flaky test quarantine in my CI/CD workflow?

Pre-merge gating enforcement and flaky test quarantine are automated guardrails designed for CI/CD workflows. They satisfy requirements for trunk-based development processes by preventing unstable code from merging and reducing false negatives in delivery pipelines.

Why do I need supply-chain provenance attestation for artifact promotion?

Supply-chain provenance attestation secures artifact promotion pipelines by verifying build origin and integrity. It satisfies delivery requirements for scoped deploy credentials and ensures shared libraries and production services have verified, traceable deployment provenance.

How do I audit my continuous delivery pipeline to reduce deployment risk?

Auditing a continuous delivery pipeline involves evaluating it against DORA metrics to find high-friction areas. You can identify the top improvements for your CI/CD setup, implement automated rollback, and decouple deploys from releases via feature flags to reduce deployment risk.