relay-recon

Map CI/CD pipelines across GitHub Actions, GitLab CI, CircleCI, and Jenkins.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map and document the full CI/CD pipeline from code commit to production, including triggers, build, test, and deploy steps, to expose configuration gaps and risks.

Core Features & Use Cases

  • Discover and map pipelines across common platforms (GitHub Actions, GitLab CI, CircleCI, Jenkins) and cloud deployment configs.
  • Trace the end-to-end flow from commit to production, capturing triggers, environments, artifacts, and rollback options.
  • Produce a concise reconnaissance report for engineers and operators to speed onboarding and handoffs.

Quick Start

Ask Relay to map your project's CI/CD pipeline and generate a risk-aware recon report.

Frequently Asked Questions about relay-recon

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

FAQPage Schema
How do I map a CI/CD pipeline from code commit to production?

To map a CI/CD pipeline, trace the end-to-end flow from code commit to production, capturing triggers, build, test, and deploy steps. This identifies configuration details, secrets usage, environments, and rollback options across your deployment configs.

Does this CI/CD pipeline mapping tool work with GitHub Actions and GitLab CI?

Yes, CI/CD pipeline mapping works across common platforms including GitHub Actions, GitLab CI, CircleCI, and Jenkins. It discovers and traces your workflows across these platforms and cloud deployment configs to document the full pipeline.

What is a CI/CD recon report and what does it include?

A CI/CD recon report documents your pipeline's end-to-end flow, capturing key requirements and risks. It includes pipeline triggers, environments, manual steps, rollback procedures, deployment timings, and configuration details to speed onboarding and handoffs.

How do I identify configuration gaps and risks in my CI/CD pipeline?

Identify configuration gaps and risks by charting the pipeline end-to-end from commit to production. Exposing configuration details, secrets usage, targets, and rollback options reveals hidden vulnerabilities and manual bottlenecks in your deployment process.

Can I trace rollback options and deployment timings across multiple cloud deployment configs?

Yes, you can trace rollback options and deployment timings across cloud deployment configs. The mapping process captures these details alongside triggers and environments, providing a complete view of deployment procedures and manual steps.

What is the best way to document CI/CD workflows for engineering handoffs?

The best way to document CI/CD workflows for handoffs is generating a concise reconnaissance report. This report maps the pipeline from commit to production, detailing triggers, environments, artifacts, and rollback options for engineers and operators.