relay-pipeline

Generate multi-stage CI/CD pipelines with install, lint, test, build, and deploy stages.

69|8|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/tonone-ai/tonone --skill relay-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: relay-pipeline
Source: https://github.com/tonone-ai/tonone/tree/main/team/relay/skills/relay-pipeline
Command: npx skills add https://github.com/tonone-ai/tonone --skill relay-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of end-to-end CI/CD pipelines from project discovery to deployment.

Core Features & Use Cases

  • Detect project stack and deployment targets, auto-select CI platform, and generate a multi-stage pipeline (Install, Lint, Test, Build, Deploy).
  • Add caching, secret handling, and environment-specific configs to ensure reliable, repeatable deployments across staging and production.
  • Use Case: When asked to "set up CI/CD" for a new project, this skill creates a ready-to-run pipeline tailored to the detected stack.

Quick Start

Set up a complete CI/CD pipeline for the current project and deploy to the detected target.

Frequently Asked Questions about relay-pipeline

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

FAQPage Schema
How do I set up an end-to-end CI/CD pipeline for a new software project?

Setting up an end-to-end CI/CD pipeline is automated by detecting your project stack and generating a multi-stage pipeline with install, lint, test, build, and deploy stages. It defaults to GitHub Actions when no existing CI configuration is detected.

Does the generated CI/CD pipeline include caching and secret handling?

The generated CI/CD pipeline includes caching, secret handling, and environment-specific configurations to ensure reliable and repeatable deployments across staging and production branches.

Can I use this to generate deployment workflows for different tech stacks?

You can generate deployment workflows for varying tech stacks because the skill automatically detects your project environment and preferred CI platform during project discovery to tailor the pipeline accordingly.

How does branch-based deployment work for staging and production environments?

Branch-based deployment is configured by applying environment-specific configs and deployment rules within the pipeline, ensuring code changes route to the correct staging or production target based on the branch.

What is the default CI platform when no existing configuration is found?

GitHub Actions is the default CI platform used when no existing configuration is found in your project. The skill generates a ready-to-run multi-stage pipeline tailored to this platform.

What stages are included in the automated CI/CD pipeline generation?

The automated CI/CD pipeline includes five distinct stages: install, lint, test, build, and deploy. This multi-stage structure ensures comprehensive validation before releasing your software.