流水线映射
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "relay-recon":https://skillpi.com/zh/skills/deepskill-3bb4502d4df2ccfd4eae800cb3730d95efd51c5e2132136dfa0a3fb3b5d87c1f。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/relay-recon/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-recon --skill relay-recon来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目介绍 流水线映射 的公开用途。DeepSkill 当前公开目录说明:“绘制完整的 CI/CD 流水线——包括触发条件、构建、测试、部署流程,并进行风险评估。适用于回答“这个是如何部署的?”、“请绘制流水线”或“了解 CI/CD”等问题。” 适用场景包括部署发布与上云。本页根据公开目录资料和固定版本的上游仓库整理,建议使用前核对该版本的环境、工具、权限及数据处理要求。Skillπ 提供站方用途介绍与原站链接;原始 SKILL.md 和附件仅在对应许可允许时开放。
文件浏览
--- name: relay-recon description: 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". allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion version: 0.6.4 author: tonone-ai <hello@tonone.ai> license: MIT --- # 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.
当前收录版本
0.6.4
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
Skill 解决 DevOps 工程师和项目接手者的实际需求,绘制完整 CI/CD 流水线并进行风险评估,实用性强。
评分依据
触发词精准完整,覆盖多种变体(如“如何部署”、“绘制流水线”),边界清晰,不易误触或漏触。
评分依据
Phase/步骤清晰(Step 0 到 Step 5),有出口条件和端到端示例,frontmatter 完整,结构规范。
评分依据
工具来源明确,参数正确,覆盖主要异常(如 2>/dev/null),不可逆操作有确认机制,执行可靠。
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
-
账号、密钥或授权
使用专用、最小权限账号,不把密钥粘贴到公开内容或命令日志;核对接收数据的服务与租户。
主文档提及 · 第 95 行
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。