skills.rest
thisrohangupta
thisrohanguptaCOMMUNITY
Explore all skills by this author →
Website𝕏@ThisRohanGuptaGitHub

migrate-pipeline

Migrates Harness pipeline definitions from v0 to v1 format.

1|Updated Apr 16, 2026
Search Tags:#Harness#pipeline migration#v0 to v1 conversion#pipeline format#code syntax transformation
One-click install
npx skills add https://github.com/thisrohangupta/cursor-harness-plugin --skill migrate-pipeline-thisrohangupta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrate-pipeline
Source: https://github.com/thisrohangupta/cursor-harness-plugin/tree/main/skills/migrate-pipeline
Command: npx skills add https://github.com/thisrohangupta/cursor-harness-plugin --skill migrate-pipeline-thisrohangupta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of migrating Harness pipelines from the older v0 format to the simplified v1 format, streamlining the process and ensuring compatibility with modern Harness features.

Core Features & Use Cases

  • Pipeline Format Migration: Converts v0 Harness pipelines to the simplified v1 format.
  • Expression Syntax Transformation: Updates expressions from angle-bracket to ${{ }} syntax.
  • Pipeline Structure Simplification: Lowercases type names and simplifies structure.
  • Variable and Logic Preservation: Retains variables, failure strategies, and conditional logic.
  • Use Case: Ideal for developers or administrators who need to upgrade pipeline formats, modernize syntax, or compare v0 and v1 pipeline capabilities.

Quick Start

Run the 'migrate-pipeline' skill to convert your Harness pipeline from v0 to v1 format.

Frequently Asked Questions about migrate-pipeline

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

FAQPage Schema
How do I migrate a Harness pipeline from v0 to v1 format?▼

Migrating a Harness pipeline from v0 to v1 format involves converting angle-bracket expressions to `${{ }}` syntax, lowercasing type names, and simplifying the overall pipeline structure for compatibility with modern Harness features.

What does Harness pipeline v0 to v1 conversion do to expression syntax?▼

Harness pipeline v0 to v1 conversion transforms expression syntax from angle-bracket formats to the simplified `${{ }}` syntax, ensuring the pipeline definitions are compatible with the latest Harness features and best practices.

Does pipeline format migration preserve variables and conditional logic?▼

Yes, pipeline format migration retains all variables, failure strategies, and conditional logic during the syntax transformation, ensuring the operational behavior of the original pipeline remains intact in the v1 format.

When do I need to convert my Harness pipeline to the v1 format?▼

You need to convert your Harness pipeline to the v1 format when seeking compatibility with modern Harness features, simplifying pipeline structure, or adopting current best practices for pipeline definitions.

What is the best way to update Harness pipeline definitions for modern syntax?▼

The best way to update Harness pipeline definitions for modern syntax is to run an automated migration that transforms v0 structures into v1 format, lowercasing type names and converting expressions to `${{ }}` syntax while preserving original elements.

Related Skills

Explore More Software Engineering Skills→
harnessharness
80

migrate-pipeline

Migrate Harness pipelines from v0 to v1 via MCP tooling.

Official
Advanced
harnessharness
80

create-pipeline-v1

Generate Harness v1 Pipeline YAML with flat structure and expressions.

Official
Advanced
thisrohanguptathisrohangupta
1

create-pipeline-v1

Generate Harness v1 Pipeline YAML with Python scripts and MCP v2 server.

Community
Advanced
dmmulroydmmulroy
1.9k

better-result-migrate-v2

Convert better-result TaggedError classes from v1 class-based to v2 factory-based API.

Community
Advanced