relay-audit
Audit an existing CI/CD pipeline for slowness, security issues, and reliability gaps. Use when asked to "audit pipeline", "why is CI slow", "pipeline review", or "deployment review".
What this skill does
# Audit Existing Pipeline 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 and deployment setup. Look for `.github/workflows/`, `.gitlab-ci.yml`, `cloudbuild.yaml`, `.circleci/`, `Jenkinsfile`, `Dockerfile`, deployment configs. ### Step 1: Read Pipeline Config Read all pipeline configuration files: ```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 ``` Also read related configs: Dockerfile, docker-compose.yml, deployment manifests, Makefile. ### Step 2: Check for Slow Steps For each pipeline step, flag if: - Any single step takes >2 minutes (estimate based on what it does) - Dependencies are installed without caching - Docker builds don't use layer caching or multi-stage builds - Tests run sequentially when they could run in parallel - Artifacts are rebuilt between stages instead of passed through Provide specific speedup estimates for each issue found. ### Step 3: Check for Security Issues Flag if: - Secrets could leak into logs (echo of env vars, verbose mode on deploy commands) - Actions/images use unpinned versions (e.g., `actions/checkout@v4` instead of SHA) - Secrets are passed as build args visible in image layers - Pipeline runs with elevated permissions unnecessarily - No branch protection or required reviews before deploy ### Step 4: Check for Reliability Issues Flag if: - No rollback procedure exists - Missing health checks or smoke tests after deploy - Environment drift — staging config differs from prod - No test stage or test stage is allowed to fail - Manual steps exist in the deployment flow - Unpinned dependency versions could cause non-deterministic builds - No concurrency controls (multiple deploys can run simultaneously) ### Step 5: Present the Audit Report Format the report as: ``` ## Pipeline Audit **Platform:** [detected CI platform] **Estimated pipeline time:** [X minutes] ### Critical (fix now) - [issue] — [specific fix] — saves ~Xmin / prevents [risk] ### Warning (fix soon) - [issue] — [specific fix] — saves ~Xmin / prevents [risk] ### Suggestion (nice to have) - [issue] — [specific fix] — saves ~Xmin / improves [area] ### What's Working Well - [positive observation] ``` Be specific — reference exact file names, line numbers, and step names. ## 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.