流水线审计

本条目介绍 流水线审计 的公开用途。DeepSkill 当前公开目录说明:“审计现有 CI/CD 流水线的运行缓慢问题、安全隐患和可靠性缺陷。适用于被要求“审计流水线”、“为什么 CI 这么慢”、“流水线审查”或“部署审查”的场景。” 适用场景包括部署发布与上云、测试与安全校验。本页根据公开目录资料和固定版本的上游仓库整理,建议使用前核对该版本的环境、工具、权限及数据处理要求。Skillπ 提供站方用途介绍与原站链接;原始 SKILL.md 和附件仅在对应许可允许时开放。

仓库
jeremylongshore/tons-of-skills-marketplace

安装方式

先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。

安装方式

用 AI 助手安装

复制提示词,让助手先核对固定版本和依赖。

查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "relay-audit":https://skillpi.com/zh/skills/deepskill-75d566543dca2d8a12f363d08c736de0d4bf837ff948be56b5da27197ade4762。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/relay-audit/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。

此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。

运行工具
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/relay-audit --skill relay-audit
许可协议: —

来源与配置

查看 GitHub 源码

jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402

配置方式待核实

请查看原始来源中的适用工具、依赖和权限要求。

安装实测待补充

本条目介绍 流水线审计 的公开用途。DeepSkill 当前公开目录说明:“审计现有 CI/CD 流水线的运行缓慢问题、安全隐患和可靠性缺陷。适用于被要求“审计流水线”、“为什么 CI 这么慢”、“流水线审查”或“部署审查”的场景。” 适用场景包括部署发布与上云、测试与安全校验。本页根据公开目录资料和固定版本的上游仓库整理,建议使用前核对该版本的环境、工具、权限及数据处理要求。Skillπ 提供站方用途介绍与原站链接;原始 SKILL.md 和附件仅在对应许可允许时开放。

↓ 0 下载 ↗ 0 分享点击

文件浏览

在原站浏览文件 ↗

原始 SKILL.md

打开原文 ↗
---
name: relay-audit
description: 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".
allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
version: 0.6.4
author: tonone-ai <hello@tonone.ai>
license: MIT
---

# 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.

当前收录版本

0.6.4

核对来源版本 ↗

质量评测

满分 100。前四项来自 DeepSkill 收录的质量报告。

场景价值85/100
评分依据

针对 CI/CD 流水线审计这一明确且高频的 DevOps 需求,实用价值高

触发精准90/100
评分依据

触发词覆盖多种常见查询场景,边界清晰,不易误触

结构规范80/100
评分依据

步骤划分清晰,有明确的输出格式规范和端到端示例

执行可靠65/100
评分依据

allowed-tools 明确,使用标准 Bash 命令,参数合理

证据可验 (前四项均值)80/100
计算方式

取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。

权限与使用前检查

根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。

未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。

本站展示提示不会授予权限。涉及文件改动、密钥、外部发送或费用时,仍由你使用的工具按需确认。

安全评级与访问范围

risk · 静态证据核验,不代表运行安全保证。

使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。

来源与使用声明 SkillPi 的部分技能资料来自公开来源或创作者提交。第三方内容的权利归各自权利人所有。安装或运行前,请查看原站的许可、权限要求和使用风险。

来源与使用

请按详情页的作者、原始来源和许可证核对使用条件,运行前检查技能需要的权限。目录收录不等于已验证安装或安全性。