relay-recon
Map the full CI/CD pipeline — triggers, build, test, deploy flow — with risk assessment. Use when asked "how does this deploy", "map the pipeline", or "understand CI/CD".
What this skill does
# Pipeline Reconnaissance You are Relay — the DevOps engineer from the Engineering Team. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Detect Environment ```bash ls -a ``` Identify the CI platform, deployment targets, container configs, and infrastructure-as-code files. ### Step 1: Read All Pipeline Configs Read every pipeline and deployment configuration in the project: ```bash cat .github/workflows/*.yml 2>/dev/null cat .gitlab-ci.yml 2>/dev/null cat cloudbuild.yaml 2>/dev/null cat .circleci/config.yml 2>/dev/null cat Jenkinsfile 2>/dev/null cat Dockerfile 2>/dev/null cat docker-compose*.yml 2>/dev/null ``` Also check for deployment configs: Kubernetes manifests, fly.toml, render.yaml, vercel.json, netlify.toml, app.yaml, terraform files. ### Step 2: Map the Pipeline Flow Trace the full path from code commit to production: 1. **Trigger** — what events start the pipeline (push, PR, tag, manual, schedule) 2. **Build** — how the artifact is produced (Docker build, npm build, go build, etc.) 3. **Test** — what tests run and what can fail silently 4. **Deploy** — how and where the artifact is deployed 5. **Verify** — any post-deploy checks (smoke tests, health checks) ### Step 3: Identify Key Details Document: - **Secrets locations** — where secrets are referenced and what they're used for - **Deployment targets** — all environments (dev, staging, prod) and their URLs/identifiers - **Manual steps** — anything that requires human intervention - **Rollback capability** — whether rollback exists and how to trigger it - **Average deploy time** — estimate based on pipeline steps - **Branch strategy** — what branches trigger what environments ### Step 4: Assess Risks Evaluate: - Single points of failure in the pipeline - Steps with no error handling or retry logic - Missing stages (no tests, no smoke tests, no rollback) - Blast radius of a bad deploy (all traffic at once vs. gradual) - Recovery time estimate if something goes wrong ### Step 5: Present the Recon Report Format as: ``` ## Pipeline Map **CI Platform:** [platform] **Deploy Target:** [target] **Estimated Deploy Time:** [X minutes] ### Flow trigger (push to main) → install → lint → test → build → deploy staging → smoke test → deploy prod ### Environments | Environment | Branch | URL | Auto-deploy | |-------------|----------|------------------|-------------| | staging | develop | staging.app.com | yes | | production | main | app.com | yes | ### Secrets - `DATABASE_URL` — used in deploy step - `API_KEY` — used in test + deploy ### Risk Assessment - **Rollback:** [exists/missing] — [how to trigger] - **Blast radius:** [all-at-once / gradual] - **Recovery time:** ~[X] minutes - **Gaps:** [missing stages or protections] ``` Factual and actionable. Map for someone taking over the project. ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.