{"id":"185bdcc9-0bcf-4a49-a17e-d7d3dbb35ab7","entityType":"agent","slug":"clawhub-kokxi-qa-ci-cd-testing","name":"qa-ci-cd-testing","canonicalUrl":"https://www.xpersona.co/agent/clawhub-kokxi-qa-ci-cd-testing","canonicalPath":"/agent/clawhub-kokxi-qa-ci-cd-testing","generatedAt":"2026-10-11T04:34:00.143Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T01:53:53.316Z","emptyReason":null},"description":"当需要把测试集成到 CI/CD 流水线中、或者现有流水线的测试环节跑起来效率低不可靠时使用此技能。覆盖流水线各阶段的分层测试卡点设计（提交检查→单元测试→接口测试→UI 测试→回归测试）、工具集成策略和质量门禁配置。不要在 CI 里堆满慢的 UI 测试——而是构建测试金字塔：提交阶段跑最快的（<5min），合码阶段跑核心的（<15min），夜间跑全量的。 触发场景：CI/CD、持续测试、流水线测试、质量门禁、自动化回归、提交即测试、构建流水线需要加入测试环节时。 Use when the user asks about: integrating tests into a CI/CD pipeline — layered quality gates, fast commit-stage tests, and release blocking criteria. Skill: qa-ci-cd-testing Owner: kokxi Summary: 当需要把测试集成到 CI/CD 流水线中、或者现有流水线的测试环节跑起来效率低不可靠时使用此技能。覆盖流水线各阶段的分层测试卡点设计（提交检查→单元测试→接口测试→UI 测试→回归测试）、工具集成策略和质量门禁配置。不要在 CI 里堆满慢的 UI 测试——而是构建测试金字塔：提交阶段跑最快的（<5min），合码阶段跑核心的（<15min），夜间跑全量的。 触发场景：CI/CD、持续测试、流水线测试、质量门禁、自动化回归、提交即测试、构建流水线需要加入测试环节时。 Use when the user asks about: integrating tests into a CI/CD pipeline — layered quality gates, fast commit-stage tests, and release blocking","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s170jw3s1atcj5jwhqb4r7v7eh8912kp:qa-ci-cd-testing","sourceUrl":"https://clawhub.ai/kokxi/qa-ci-cd-testing","homepage":"https://clawhub.ai/kokxi/skills/qa-ci-cd-testing","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/kokxi/qa-ci-cd-testing","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/kokxi/skills/qa-ci-cd-testing","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":62,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"当需要把测试集成到 CI/CD 流水线中、或者现有流水线的测试环节跑起来效率低不可靠时使用此技能。覆盖流水线各阶段的分层测试卡点设计（提交检查→单元测试→接口测试→UI 测试→回归测试）、工具集成策略和质量门禁配置。不要在 CI 里堆满慢的 UI 测试——而是构建测试金字塔：提交阶段跑最快的（<5min），合码阶段跑核"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T01:53:53.316Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T01:53:53.316Z","emptyReason":null},"stars":null,"forks":null,"downloads":1199,"packageName":null,"latestVersion":"1.8.0","tractionLabel":"1.2K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T01:53:53.303Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T01:53:53.316Z","lastCrawledAt":"2026-10-11T01:53:53.303Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T01:53:53.303Z","lastVerifiedAt":null,"highlights":[{"version":"1.8.0","createdAt":"2026-09-29T04:25:55.679Z","changelog":"Version 1.8.0 summary: Refactored structure and improved modularity for pipeline design content. - Moved detailed CI/CD 流水线设计内容 to a separate reference file (`references/pipeline-design.md`) for better maintainability. - Updated SKILL.md metadata fields and structure, including a more concise description and new metadata blocks. - Added \"加载时机\" section to clarify when to load reference materials. - Removed the legacy skill-card.md file. - Minor language and formatting improvements for clarity and context efficiency.","fileCount":4,"zipByteSize":5566},{"version":"1.7.7","createdAt":"2026-09-27T14:33:38.551Z","changelog":"1.7.7","fileCount":3,"zipByteSize":4809},{"version":"1.7.6","createdAt":"2026-09-01T12:37:46.224Z","changelog":"显示名改中文","fileCount":3,"zipByteSize":5119},{"version":"1.7.5","createdAt":"2026-08-30T15:12:16.075Z","changelog":"1.7.5: 版本号升级","fileCount":3,"zipByteSize":4934},{"version":"1.6.3","createdAt":"2026-08-12T15:22:05.180Z","changelog":"- Added slug and displayName fields to metadata for improved identification. - Updated version number to 1.6.3. - skill-card.md file was removed. - No functional changes to the skill logic or procedural content.","fileCount":3,"zipByteSize":4571},{"version":"1.6.0","createdAt":"2026-07-06T17:14:42.953Z","changelog":"- Added traceability support: each pipeline now includes a unique ID (PIPE-XXXX). - Enhanced output format to clarify structure and traceability. - Expanded upstream/downstream related_skills, adding qa-shift-right as downstream. - Added skill categories (Development, Testing, DevOps). - Introduced quantification guidelines for required depth based on pipeline complexity. - Added error recovery guidance for pipeline failures and retry behavior. - Updated \"when_to_use\" to clarify triggers for skill usage. - Removed skill-card.md file.","fileCount":3,"zipByteSize":4760},{"version":"1.5.0","createdAt":"2026-06-29T12:31:59.599Z","changelog":"Version 1.5.0 - Output结构化：明确output_format，包括pipeline_design、test_stages、quality_gates、feedback_loops等字段。 - 精简与聚焦描述，突出实际CI/CD测试效率与金字塔分层思想，强调各阶段运行时间指标。 - 增加版本字段和输入要求说明，区分必选/可选输入，对接相关上游技能。 - 移除冗余内容和skill-card.md文件，优化上下游关联逻辑。 - 保留原有左移/右移分块与示例，新增项目分级质量门禁表，增强方案落地指导性。","fileCount":3,"zipByteSize":4415},{"version":"1.4.1","createdAt":"2026-06-25T16:53:50.998Z","changelog":"- skill-card.md 文件已移除，精简了文件结构。 - SKILL.md 中描述大幅优化，聚焦于持续测试集成、流水线设计、工具集成和质量门禁配置。 - 说明内容更聚焦测试接入及优化场景，简化用语并删减部分细节。 - 更明确了触发条件和核心覆盖内容。","fileCount":3,"zipByteSize":3690}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s170jw3s1atcj5jwhqb4r7v7eh8912kp:qa-ci-cd-testing","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-ci-cd-testing/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-ci-cd-testing/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-ci-cd-testing/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-ci-cd-testing/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-ci-cd-testing/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-ci-cd-testing/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T04:34:00.142Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-ci-cd-testing/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-ci-cd-testing/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-ci-cd-testing/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kokxi-qa-ci-cd-testing/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T01:53:53.316Z","emptyReason":null},"readme":"Skill: qa-ci-cd-testing\n\nOwner: kokxi\n\nSummary: 当需要把测试集成到 CI/CD 流水线中、或者现有流水线的测试环节跑起来效率低不可靠时使用此技能。覆盖流水线各阶段的分层测试卡点设计（提交检查→单元测试→接口测试→UI 测试→回归测试）、工具集成策略和质量门禁配置。不要在 CI 里堆满慢的 UI 测试——而是构建测试金字塔：提交阶段跑最快的（<5min），合码阶段跑核心的（<15min），夜间跑全量的。 触发场景：CI/CD、持续测试、流水线测试、质量门禁、自动化回归、提交即测试、构建流水线需要加入测试环节时。 Use when the user asks about: integrating tests into a CI/CD pipeline — layered quality gates, fast commit-stage tests, and release blocking criteria.\n\nTags: latest:1.8.0\n\nVersion history:\n\nv1.8.0 | 2026-09-29T04:25:55.679Z | auto\n\nVersion 1.8.0 summary: Refactored structure and improved modularity for pipeline design content.\n\n- Moved detailed CI/CD 流水线设计内容 to a separate reference file (`references/pipeline-design.md`) for better maintainability.\n- Updated SKILL.md metadata fields and structure, including a more concise description and new metadata blocks.\n- Added \"加载时机\" section to clarify when to load reference materials.\n- Removed the legacy skill-card.md file.\n- Minor language and formatting improvements for clarity and context efficiency.\n\nv1.7.7 | 2026-09-27T14:33:38.551Z | user\n\n1.7.7\n\nv1.7.6 | 2026-09-01T12:37:46.224Z | user\n\n显示名改中文\n\nv1.7.5 | 2026-08-30T15:12:16.075Z | user\n\n1.7.5: 版本号升级\n\nv1.6.3 | 2026-08-12T15:22:05.180Z | auto\n\n- Added slug and displayName fields to metadata for improved identification.\n- Updated version number to 1.6.3.\n- skill-card.md file was removed.\n- No functional changes to the skill logic or procedural content.\n\nv1.6.0 | 2026-07-06T17:14:42.953Z | auto\n\n- Added traceability support: each pipeline now includes a unique ID (PIPE-XXXX).\n- Enhanced output format to clarify structure and traceability.\n- Expanded upstream/downstream related_skills, adding qa-shift-right as downstream.\n- Added skill categories (Development, Testing, DevOps).\n- Introduced quantification guidelines for required depth based on pipeline complexity.\n- Added error recovery guidance for pipeline failures and retry behavior.\n- Updated \"when_to_use\" to clarify triggers for skill usage.\n- Removed skill-card.md file.\n\nv1.5.0 | 2026-06-29T12:31:59.599Z | auto\n\nVersion 1.5.0\n\n- Output结构化：明确output_format，包括pipeline_design、test_stages、quality_gates、feedback_loops等字段。\n- 精简与聚焦描述，突出实际CI/CD测试效率与金字塔分层思想，强调各阶段运行时间指标。\n- 增加版本字段和输入要求说明，区分必选/可选输入，对接相关上游技能。\n- 移除冗余内容和skill-card.md文件，优化上下游关联逻辑。\n- 保留原有左移/右移分块与示例，新增项目分级质量门禁表，增强方案落地指导性。\n\nv1.4.1 | 2026-06-25T16:53:50.998Z | auto\n\n- skill-card.md 文件已移除，精简了文件结构。\n- SKILL.md 中描述大幅优化，聚焦于持续测试集成、流水线设计、工具集成和质量门禁配置。\n- 说明内容更聚焦测试接入及优化场景，简化用语并删减部分细节。\n- 更明确了触发条件和核心覆盖内容。\n\nv1.4.0 | 2026-06-24T05:06:02.968Z | auto\n\n- Expanded the skill description and activation keywords for broader CI/CD testing and pipeline optimization scenarios.\n- Improved documentation with a new \"Overview\" section and two practical examples for common CI/CD integration and optimization cases.\n- Streamlined skill guidance and checklists under a \"Guidelines\" section.\n- Removed unnecessary file: skill-card.md.\n\nv1.3.0 | 2026-06-21T15:37:47.435Z | auto\n\n- Expanded SKILL.md with detailed CI/CD测试方案实践、流程分解、质量门禁与工具选型说明\n- 明确左移和右移测试策略及具体落地实践\n- 增加CI/CD流水线各阶段职责和质量门禁标准\n- 补充主流工具选型建议及验收清单，以便实施检查\n\nArchive index:\n\nArchive v1.8.0: 4 files, 5566 bytes\n\nFiles: references/pipeline-design.md (1975b), skill-card.md (1739b), SKILL.md (6765b), _meta.json (135b)\n\nFile v1.8.0:SKILL.md\n\n---\nname: qa-ci-cd-testing\ndescription: >-\n  当需要把测试集成到 CI/CD 流水线中、或者现有流水线的测试环节跑起来效率低不可靠时使用此技能。覆盖流水线各阶段的分层测试卡点设计（提交检查→单元测试→接口测试→UI 测试→回归测试）、工具集成策略和质量门禁配置。不要在 CI 里堆满慢的 UI 测试——而是构建测试金字塔：提交阶段跑最快的（<5min），合码阶段跑核心的（<15min），夜间跑全量的。 触发场景：CI/CD、持续测试、流水线测试、质量门禁、自动化回归、提交即测试、构建流水线需要加入测试环节时。 Use when the user asks about: integrating tests into a CI/CD pipeline — layered quality gates, fast commit-stage tests, and release blocking criteria.\nlicense: MIT\nallowed-tools: Read Grep Glob Bash\nmetadata:\n  display-name: \"Ci Cd Testing\"\n  version: \"1.8.0\"\n  when-to-use: \"用户说\\\"CI/CD\\\"、\\\"持续测试\\\"、\\\"流水线测试\\\"、\\\"质量门禁\\\"、\\\"自动化回归\\\"、\\\"提交即测试\\\"、需要设计CI/CD测试流程、构建流水线需要加入测试环节时\"\n  related-skills: \"{\\\"upstream\\\":[\\\"qa-tech-selection\\\",\\\"qa-test-strategy-design\\\"],\\\"downstream\\\":[\\\"qa-release-risk-governance\\\",\\\"qa-shift-right\\\"]}\"\n  references: \"[\\\"references/pipeline-design.md\\\"]\"\n  input-format: \"{\\\"required\\\":[{\\\"name\\\":\\\"测试策略\\\",\\\"type\\\":\\\"object\\\",\\\"description\\\":\\\"来自qa-test-strategy-design的测试策略\\\"},{\\\"name\\\":\\\"自动化架构\\\",\\\"type\\\":\\\"object\\\",\\\"description\\\":\\\"来自qa-test-automation-arch的自动化架构\\\"}],\\\"optional\\\":[{\\\"name\\\":\\\"流水线配置\\\",\\\"type\\\":\\\"string\\\",\\\"description\\\":\\\"CI/CD流水线配置信息\\\"}]}\"\n  output-format: \"{\\\"traceability\\\":[\\\"每条流水线带唯一ID（PIPE-XXXX）\\\"],\\\"structure\\\":[\\\"覆盖率：标注口径（基于现有需求/输入文档），禁止\\\\\\\"全覆盖/100%\\\\\\\"绝对化表述；缺失模块标注\\\\\\\"未覆盖+原因\\\\\\\"\\\",{\\\"pipeline_design\\\":\\\"CI/CD流水线设计\\\"},{\\\"test_stages\\\":\\\"各阶段测试配置\\\"},{\\\"quality_gates\\\":\\\"质量门禁设置\\\"},{\\\"feedback_loops\\\":\\\"反馈循环机制\\\"}]}\"\n  error-recovery-guidance: \"{\\\"on_failure\\\":\\\"流水线测试卡点失败时回退到测试策略调整范围\\\",\\\"retry_behavior\\\":\\\"调整测试范围或工具后重新配置卡点\\\"}\"\n  categories: \"[\\\"Development\\\",\\\"Testing\\\",\\\"DevOps\\\"]\"\n  depth-requirement: \"{\\\"reference_value\\\":\\\"根据流水线复杂度调整设计深度：简单×1/中等×2/复杂×3\\\",\\\"minimum\\\":\\\"至少覆盖提交检查、接口测试、回归测试3个卡点\\\"}\"\n---\n> ⚠️ 本技能单独使用效果有限，建议配合完整技能集（12 步工作流）使用。安装：npx skills add Kokxi/qa-test-skills\n\n> **⚠️ 安全警告**：本技能的示例可能涉及 CI/CD 流水线配置、发布操作和部署环境。\n> 实际使用时请勿在未授权的生产环境执行发布或部署，先确认灰度策略和回滚方案。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 持续测试实践\n\n## 核心原则\n\n测试左移（提前测试）、测试右移（线上验证）、快速反馈。\n\n## 深度要求（参考值）\n\n**关键指标**：根据项目复杂度设计质量门禁策略\n\n| 复杂度 | 流水线阶段 | 质量门禁阈值 | 说明 |\n|--------|-----------|-------------|------|\n| 简单项目 | 2-3个阶段 | 单元测试通过率≥80% | 标准CI流程 |\n| 中等项目 | 4-5个阶段 | 单元≥90%+接口通过率≥95% | 含集成测试 |\n| 复杂项目 | 6-8个阶段 | 全链路≥95%+性能阈值 | 含全量自动化+安全扫描 |\n\n## 测试左移\n\n### 左移策略\n\n```text\n需求阶段：\n├─ 需求评审：测试参与需求评审\n├─ 验收标准：明确验收条件\n├─ 可测试性：评估可测试性\n└─ 测试计划：制定测试计划\n\n开发阶段：\n├─ 代码评审：测试视角的CR\n├─ 单元测试：开发编写单元测试\n├─ 接口测试：测试编写接口测试\n└─ 冒烟测试：开发自测通过\n\n集成阶段：\n├─ 接口自动化：自动执行接口测试\n├─ 集成测试：自动执行集成测试\n└─ 冒烟测试：自动执行冒烟测试\n```\n\n### 左移实践\n\n```text\n实践1：需求可测试性评估\n├─ 验收条件是否明确？\n├─ 是否可自动化验证？\n├─ 测试数据是否可准备？\n└─ 测试环境是否可搭建？\n\n实践2：代码评审检查点\n├─ 业务逻辑是否正确？\n├─ 异常处理是否完善？\n├─ 日志记录是否完整？\n└─ 测试代码是否同步？\n\n实践3：单元测试覆盖\n├─ 核心逻辑单元测试\n├─ 分支覆盖\n├─ 边界覆盖\n└─ 异常覆盖\n```\n\n## 测试右移\n\n### 右移策略\n\n```text\n发布阶段：\n├─ 灰度发布：按比例放量\n├─ 监控告警：实时监控\n├─ 快速回滚：问题时快速回滚\n└─ 线上验证：验证发布效果\n\n线上阶段：\n├─ 业务监控：业务指标监控\n├─ 技术监控：技术指标监控\n├─ 用户反馈：用户问题收集\n└─ 混沌工程：主动注入故障\n```\n\n### 右移实践\n\n```text\n实践1：灰度发布\n├─ 用户灰度：按用户比例\n├─ 流量灰度：按流量比例\n├─ 地域灰度：按地域\n└─ 监控验证：实时监控\n\n实践2：线上监控\n├─ 业务监控：订单量、成功率\n├─ 技术监控：错误率、响应时间\n├─ 资源监控：CPU、内存、磁盘\n└─ 告警通知：异常告警\n\n实践3：混沌工程\n├─ 故障注入：模拟故障\n├─ 韧性验证：验证系统韧性\n├─ 恢复测试：验证恢复能力\n└─ 改进优化：持续改进\n```\n\n## 加载时机\n\n| 什么时候读 | 读哪个 |\n|-----------|--------|\n| 设计流水线分层卡点时 | [`references/pipeline-design.md`](references/pipeline-design.md) |\n\n> `CI/CD 流水线设计`的完整内容已下沉至 `references/pipeline-design.md`，避免每次触发都占用上下文。\n\n## 输出示例\n\n**团队需要将测试接入CI/CD流水线**\n→ 设计流水线阶段：提交触发→单元测试→接口测试→UI测试→质量门禁→报告\n→ 左移：需求阶段定义验收标准，开发阶段推动单元测试\n→ 右移：灰度发布监控指标，线上质量监控告警\n\n**现有CI/CD测试效率低下（跑一次1小时）**\n→ 优化策略：分层并行执行、增量测试、智能用例筛选\n\n## 检查清单\n\n持续测试实践完成后检查：\n- [ ] 测试左移是否实施？\n- [ ] 测试右移是否规划？\n- [ ] CI/CD流水线是否设计？\n- [ ] 质量门禁是否定义？\n- [ ] 工具选型是否完成？\n- [ ] 监控告警是否配置？\n\nFile v1.8.0:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-ci-cd-testing\",\n  \"version\": \"1.8.0\",\n  \"publishedAt\": 1790655955679\n}\n\nFile v1.8.0:references/pipeline-design.md\n\n# CI/CD 流水线设计详解\n\n> 本文是 `qa-ci-cd-testing` 的**CI/CD 流水线设计详解**。设计流水线分层卡点时读本文；\n其余部分留在 SKILL.md，不必读本文。\n\n---\n\n\n### 流水线阶段\n\n```text\n代码提交 → 代码检查 → 单元测试 → 接口测试 → 集成测试 → 部署 → 冒烟测试 → 灰度发布 → 全量发布\n\n各阶段职责：\n├─ 代码提交：提交代码\n├─ 代码检查：静态代码分析\n├─ 单元测试：执行单元测试\n├─ 接口测试：执行接口测试\n├─ 集成测试：执行集成测试\n├─ 部署：部署到测试环境\n├─ 冒烟测试：执行冒烟测试\n├─ 灰度发布：按比例发布\n└─ 全量发布：全量发布\n```\n\n### 质量门禁\n\n```text\n门禁标准：\n├─ 代码检查\n│   ├─ 代码规范：无严重违规\n│   ├─ 代码重复：< 5%\n│   └─ 圈复杂度：< 10\n│\n├─ 单元测试\n│   ├─ 覆盖率：≥ 80%\n│   ├─ 通过率：100%\n│   └─ 执行时间：< 5分钟\n│\n├─ 接口测试\n│   ├─ 覆盖率：≥ 90%\n│   ├─ 通过率：100%\n│   └─ 执行时间：< 10分钟\n│\n├─ 集成测试\n│   ├─ 通过率：100%\n│   └─ 执行时间：< 30分钟\n│\n└─ 冒烟测试\n    ├─ 通过率：100%\n    └─ 核心功能：全部通过\n```\n\n### 工具选型\n\n```text\n├─ 代码管理\n│   ├─ Git：版本控制\n│   └─ GitLab/GitHub：代码托管\n│\n├─ CI/CD工具\n│   ├─ Jenkins：开源、灵活\n│   ├─ GitLab CI：集成度高\n│   ├─ GitHub Actions：云端友好\n│   └─ CircleCI：云端CI\n│\n├─ 测试工具\n│   ├─ JUnit/TestNG：单元测试\n│   ├─ Pytest：Python测试\n│   ├─ Postman/Newman：接口测试\n│   └─ Selenium/Playwright：UI测试\n│\n└─ 报告工具\n    ├─ Allure：测试报告\n    ├─ SonarQube：代码质量\n    └─ Grafana：监控可视化\n```\n\nFile v1.8.0:skill-card.md\n\n## Description:\n\nHelps teams design staged CI/CD testing, quality gates, and feedback loops for faster, more reliable releases.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and QA engineers use this skill to plan layered tests, quality gates, and release feedback across CI/CD stages, including fast commit checks and regression testing.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The optional installation command fetches an unpinned skill package.\n\nMitigation: Review the command and package before using it.\n\nRisk: Applying deployment or release recommendations without safeguards could affect production systems.\n\nMitigation: Use only in authorized environments with a reviewed rollout and rollback plan.\n\n## Reference(s):\n\n- [CI/CD pipeline design reference](references/pipeline-design.md)\n- [ClawHub skill release](https://clawhub.ai/kokxi/skills/qa-ci-cd-testing)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Configuration instructions, Markdown]\n\n**Output Format:** [Markdown pipeline design with test stages, quality gates, and feedback loops]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Pipeline IDs use PIPE-XXXX; coverage statements identify their basis and explain uncovered modules.]\n\n## Skill Version(s):\n\n1.8.0 (source: skill frontmatter and server release)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.7.7: 3 files, 4809 bytes\n\nFiles: skill-card.md (1576b), SKILL.md (8079b), _meta.json (135b)\n\nFile v1.7.7:SKILL.md\n\n---\nname: qa-ci-cd-testing\nslug: qa-ci-cd-testing\ndisplayName: Ci Cd Testing\nversion: 1.7.7\ndescription: >-\n  当需要把测试集成到 CI/CD 流水线中、或者现有流水线的测试环节跑起来效率低不可靠时使用此技能。覆盖流水线各阶段的分层测试卡点设计（提交检查→单元测试→接口测试→UI 测试→回归测试）、工具集成策略和质量门禁配置。不要在 CI 里堆满慢的 UI 测试——而是构建测试金字塔：提交阶段跑最快的（<5min），合码阶段跑核心的（<15min），夜间跑全量的。\n\nwhen_to_use: 用户说\"CI/CD\"、\"持续测试\"、\"流水线测试\"、\"质量门禁\"、\"自动化回归\"、\"提交即测试\"、需要设计CI/CD测试流程、构建流水线需要加入测试环节时\nallowed-tools: Read Grep Glob Bash\nrelated_skills:\n  upstream:\n    - qa-tech-selection          # 输入：技术选型确定工具栈\n    - qa-test-strategy-design    # 输入：测试策略确定自动化范围\n  downstream:\n    - qa-release-risk-governance # 输出：CI/CD流程支持发布\n    - qa-shift-right\ninput_format:\n  required:\n    - name: 测试策略\n      type: object\n      description: 来自qa-test-strategy-design的测试策略\n    - name: 自动化架构\n      type: object\n      description: 来自qa-test-automation-arch的自动化架构\n  optional:\n    - name: 流水线配置\n      type: string\n      description: CI/CD流水线配置信息\noutput_format:\n  traceability:\n    - 每条流水线带唯一ID（PIPE-XXXX）\n  structure:\n    - 测试用例表格：固定 9 列（用例编号|测试类型|功能模块|测试标题|用例级别|预置条件|测试步骤|预期结果|风险等级）\n    - 用例级别：P0≤20%（核心流程）/ P1≤40%（主要功能）/ P2≤30%（次要功能）/ P3≤10%（边缘场景）\n    - 覆盖率：标注口径（基于现有需求/输入文档），禁止\"全覆盖/100%\"绝对化表述；缺失模块标注\"未覆盖+原因\"\n    - pipeline_design: CI/CD流水线设计\n    - test_stages: 各阶段测试配置\n    - quality_gates: 质量门禁设置\n    - feedback_loops: 反馈循环机制\ncategories: ['Development','Testing','DevOps']\ndepth_requirement_quantification:\n  reference_value: \"根据流水线复杂度调整设计深度：简单×1/中等×2/复杂×3\"\n  minimum: \"至少覆盖提交检查、接口测试、回归测试3个卡点\"\nerror_recovery_guidance:\n  on_failure: \"流水线测试卡点失败时回退到测试策略调整范围\"\n  retry_behavior: \"调整测试范围或工具后重新配置卡点\"\n---\n> **⚠️ 安全警告**：本技能的示例可能涉及 CI/CD 流水线配置、发布操作和部署环境。\n> 实际使用时请勿在未授权的生产环境执行发布或部署，先确认灰度策略和回滚方案。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 持续测试实践\n\n## 核心原则\n\n测试左移（提前测试）、测试右移（线上验证）、快速反馈。\n\n## 深度要求（参考值）\n\n**关键指标**：根据项目复杂度设计质量门禁策略\n\n| 复杂度 | 流水线阶段 | 质量门禁阈值 | 说明 |\n|--------|-----------|-------------|------|\n| 简单项目 | 2-3个阶段 | 单元测试通过率≥80% | 标准CI流程 |\n| 中等项目 | 4-5个阶段 | 单元≥90%+接口通过率≥95% | 含集成测试 |\n| 复杂项目 | 6-8个阶段 | 全链路≥95%+性能阈值 | 含全量自动化+安全扫描 |\n\n## 测试左移\n\n### 左移策略\n\n```text\n需求阶段：\n├─ 需求评审：测试参与需求评审\n├─ 验收标准：明确验收条件\n├─ 可测试性：评估可测试性\n└─ 测试计划：制定测试计划\n\n开发阶段：\n├─ 代码评审：测试视角的CR\n├─ 单元测试：开发编写单元测试\n├─ 接口测试：测试编写接口测试\n└─ 冒烟测试：开发自测通过\n\n集成阶段：\n├─ 接口自动化：自动执行接口测试\n├─ 集成测试：自动执行集成测试\n└─ 冒烟测试：自动执行冒烟测试\n```\n\n### 左移实践\n\n```text\n实践1：需求可测试性评估\n├─ 验收条件是否明确？\n├─ 是否可自动化验证？\n├─ 测试数据是否可准备？\n└─ 测试环境是否可搭建？\n\n实践2：代码评审检查点\n├─ 业务逻辑是否正确？\n├─ 异常处理是否完善？\n├─ 日志记录是否完整？\n└─ 测试代码是否同步？\n\n实践3：单元测试覆盖\n├─ 核心逻辑单元测试\n├─ 分支覆盖\n├─ 边界覆盖\n└─ 异常覆盖\n```\n\n## 测试右移\n\n### 右移策略\n\n```text\n发布阶段：\n├─ 灰度发布：按比例放量\n├─ 监控告警：实时监控\n├─ 快速回滚：问题时快速回滚\n└─ 线上验证：验证发布效果\n\n线上阶段：\n├─ 业务监控：业务指标监控\n├─ 技术监控：技术指标监控\n├─ 用户反馈：用户问题收集\n└─ 混沌工程：主动注入故障\n```\n\n### 右移实践\n\n```text\n实践1：灰度发布\n├─ 用户灰度：按用户比例\n├─ 流量灰度：按流量比例\n├─ 地域灰度：按地域\n└─ 监控验证：实时监控\n\n实践2：线上监控\n├─ 业务监控：订单量、成功率\n├─ 技术监控：错误率、响应时间\n├─ 资源监控：CPU、内存、磁盘\n└─ 告警通知：异常告警\n\n实践3：混沌工程\n├─ 故障注入：模拟故障\n├─ 韧性验证：验证系统韧性\n├─ 恢复测试：验证恢复能力\n└─ 改进优化：持续改进\n```\n\n## CI/CD 流水线设计\n\n### 流水线阶段\n\n```text\n代码提交 → 代码检查 → 单元测试 → 接口测试 → 集成测试 → 部署 → 冒烟测试 → 灰度发布 → 全量发布\n\n各阶段职责：\n├─ 代码提交：提交代码\n├─ 代码检查：静态代码分析\n├─ 单元测试：执行单元测试\n├─ 接口测试：执行接口测试\n├─ 集成测试：执行集成测试\n├─ 部署：部署到测试环境\n├─ 冒烟测试：执行冒烟测试\n├─ 灰度发布：按比例发布\n└─ 全量发布：全量发布\n```\n\n### 质量门禁\n\n```text\n门禁标准：\n├─ 代码检查\n│   ├─ 代码规范：无严重违规\n│   ├─ 代码重复：< 5%\n│   └─ 圈复杂度：< 10\n│\n├─ 单元测试\n│   ├─ 覆盖率：≥ 80%\n│   ├─ 通过率：100%\n│   └─ 执行时间：< 5分钟\n│\n├─ 接口测试\n│   ├─ 覆盖率：≥ 90%\n│   ├─ 通过率：100%\n│   └─ 执行时间：< 10分钟\n│\n├─ 集成测试\n│   ├─ 通过率：100%\n│   └─ 执行时间：< 30分钟\n│\n└─ 冒烟测试\n    ├─ 通过率：100%\n    └─ 核心功能：全部通过\n```\n\n### 工具选型\n\n```text\n├─ 代码管理\n│   ├─ Git：版本控制\n│   └─ GitLab/GitHub：代码托管\n│\n├─ CI/CD工具\n│   ├─ Jenkins：开源、灵活\n│   ├─ GitLab CI：集成度高\n│   ├─ GitHub Actions：云端友好\n│   └─ CircleCI：云端CI\n│\n├─ 测试工具\n│   ├─ JUnit/TestNG：单元测试\n│   ├─ Pytest：Python测试\n│   ├─ Postman/Newman：接口测试\n│   └─ Selenium/Playwright：UI测试\n│\n└─ 报告工具\n    ├─ Allure：测试报告\n    ├─ SonarQube：代码质量\n    └─ Grafana：监控可视化\n```\n\n## 输出示例\n\n**团队需要将测试接入CI/CD流水线**\n→ 设计流水线阶段：提交触发→单元测试→接口测试→UI测试→质量门禁→报告\n→ 左移：需求阶段定义验收标准，开发阶段推动单元测试\n→ 右移：灰度发布监控指标，线上质量监控告警\n\n**现有CI/CD测试效率低下（跑一次1小时）**\n→ 优化策略：分层并行执行、增量测试、智能用例筛选\n\n## 检查清单\n\n持续测试实践完成后检查：\n- [ ] 测试左移是否实施？\n- [ ] 测试右移是否规划？\n- [ ] CI/CD流水线是否设计？\n- [ ] 质量门禁是否定义？\n- [ ] 工具选型是否完成？\n- [ ] 监控告警是否配置？\n\nFile v1.7.7:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-ci-cd-testing\",\n  \"version\": \"1.7.7\",\n  \"publishedAt\": 1790519618551\n}\n\nFile v1.7.7:skill-card.md\n\n## Description:\n\nProvides Chinese-language guidance for integrating layered tests and quality gates into CI/CD pipelines.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and QA engineers use this skill to plan CI/CD test stages, select testing tools, set quality gates, and improve feedback from commits through release.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Applying suggested pipeline or deployment changes without review could affect a live environment.\n\nMitigation: Review generated configuration and commands, obtain authorization before pipeline changes, and confirm rollout and rollback plans before deployment.\n\n## Reference(s):\n\n- [ClawHub skill release](https://clawhub.ai/kokxi/skills/qa-ci-cd-testing)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Configuration guidance]\n\n**Output Format:** [Markdown guidance with pipeline stages, test checkpoints, and quality gates]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Chinese-language guidance; pipeline designs can include PIPE-XXXX identifiers and test-case tables.]\n\n## Skill Version(s):\n\n1.7.7 (source: ClawHub release and skill frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.7.6: 3 files, 5119 bytes\n\nFiles: skill-card.md (1854b), SKILL.md (8617b), _meta.json (135b)\n\nFile v1.7.6:SKILL.md\n\n---\r\nname: qa-ci-cd-testing\r\nslug: qa-ci-cd-testing\r\ndisplayName: CI/CD 测试\r\nversion: 1.7.5\r\ndescription: >-\r\n  当需要把测试集成到 CI/CD 流水线中、或者现有流水线的测试环节跑起来效率低不可靠时使用此技能。覆盖流水线各阶段的分层测试卡点设计（提交检查→单元测试→接口测试→UI 测试→回归测试）、工具集成策略和质量门禁配置。不要在 CI 里堆满慢的 UI 测试——而是构建测试金字塔：提交阶段跑最快的（<5min），合码阶段跑核心的（<15min），夜间跑全量的。\r\n  本技能属于 QA Test Skills 技能集（49 个技能之一），完整工作流体验需安装全套：npx skills add Kokxi/qa-test-skills\r\n\r\nwhen_to_use: 用户说\"CI/CD\"、\"持续测试\"、\"流水线测试\"、\"质量门禁\"、\"自动化回归\"、\"提交即测试\"、需要设计CI/CD测试流程、构建流水线需要加入测试环节时\r\nallowed-tools: Read Grep Glob Bash\r\nrelated_skills:\r\n  upstream:\r\n    - qa-tech-selection          # 输入：技术选型确定工具栈\r\n    - qa-test-strategy-design    # 输入：测试策略确定自动化范围\r\n  downstream:\r\n    - qa-release-risk-governance # 输出：CI/CD流程支持发布\r\n    - qa-shift-right\r\ninput_format:\r\n  required:\r\n    - name: 测试策略\r\n      type: object\r\n      description: 来自qa-test-strategy-design的测试策略\r\n    - name: 自动化架构\r\n      type: object\r\n      description: 来自qa-test-automation-arch的自动化架构\r\n  optional:\r\n    - name: 流水线配置\r\n      type: string\r\n      description: CI/CD流水线配置信息\r\noutput_format:\r\n  traceability:\r\n    - 每条流水线带唯一ID（PIPE-XXXX）\r\n  structure:\r\n    - 测试用例表格：固定 9 列（用例编号|测试类型|功能模块|测试标题|用例级别|预置条件|测试步骤|预期结果|风险等级）\r\n    - 用例级别：P0≤20%（核心流程）/ P1≤40%（主要功能）/ P2≤30%（次要功能）/ P3≤10%（边缘场景）\r\n    - 覆盖率：标注口径（基于现有需求/输入文档），禁止\"全覆盖/100%\"绝对化表述；缺失模块标注\"未覆盖+原因\"\r\n    - pipeline_design: CI/CD流水线设计\r\n    - test_stages: 各阶段测试配置\r\n    - quality_gates: 质量门禁设置\r\n    - feedback_loops: 反馈循环机制\r\ncategories: ['Development','Testing','DevOps']\r\ndepth_requirement_quantification:\r\n  reference_value: \"根据流水线复杂度调整设计深度：简单×1/中等×2/复杂×3\"\r\n  minimum: \"至少覆盖提交检查、接口测试、回归测试3个卡点\"\r\nerror_recovery_guidance:\r\n  on_failure: \"流水线测试卡点失败时回退到测试策略调整范围\"\r\n  retry_behavior: \"调整测试范围或工具后重新配置卡点\"\r\n---\r\n> ⚠️ 本技能单独使用效果有限，建议配合完整技能集（12 步工作流）使用。安装：npx skills add Kokxi/qa-test-skills\r\n\r\n> **⚠️ 安全警告**：本技能的示例可能涉及 CI/CD 流水线配置、发布操作和部署环境。\r\n> 实际使用时请勿在未授权的生产环境执行发布或部署，先确认灰度策略和回滚方案。\r\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\r\n\r\n# 持续测试实践\r\n\r\n## 核心原则\r\n\r\n测试左移（提前测试）、测试右移（线上验证）、快速反馈。\r\n\r\n## 深度要求（参考值）\r\n\r\n**关键指标**：根据项目复杂度设计质量门禁策略\r\n\r\n| 复杂度 | 流水线阶段 | 质量门禁阈值 | 说明 |\r\n|--------|-----------|-------------|------|\r\n| 简单项目 | 2-3个阶段 | 单元测试通过率≥80% | 标准CI流程 |\r\n| 中等项目 | 4-5个阶段 | 单元≥90%+接口通过率≥95% | 含集成测试 |\r\n| 复杂项目 | 6-8个阶段 | 全链路≥95%+性能阈值 | 含全量自动化+安全扫描 |\r\n\r\n## 测试左移\r\n\r\n### 左移策略\r\n\r\n```text\r\n需求阶段：\r\n├─ 需求评审：测试参与需求评审\r\n├─ 验收标准：明确验收条件\r\n├─ 可测试性：评估可测试性\r\n└─ 测试计划：制定测试计划\r\n\r\n开发阶段：\r\n├─ 代码评审：测试视角的CR\r\n├─ 单元测试：开发编写单元测试\r\n├─ 接口测试：测试编写接口测试\r\n└─ 冒烟测试：开发自测通过\r\n\r\n集成阶段：\r\n├─ 接口自动化：自动执行接口测试\r\n├─ 集成测试：自动执行集成测试\r\n└─ 冒烟测试：自动执行冒烟测试\r\n```\r\n\r\n### 左移实践\r\n\r\n```text\r\n实践1：需求可测试性评估\r\n├─ 验收条件是否明确？\r\n├─ 是否可自动化验证？\r\n├─ 测试数据是否可准备？\r\n└─ 测试环境是否可搭建？\r\n\r\n实践2：代码评审检查点\r\n├─ 业务逻辑是否正确？\r\n├─ 异常处理是否完善？\r\n├─ 日志记录是否完整？\r\n└─ 测试代码是否同步？\r\n\r\n实践3：单元测试覆盖\r\n├─ 核心逻辑单元测试\r\n├─ 分支覆盖\r\n├─ 边界覆盖\r\n└─ 异常覆盖\r\n```\r\n\r\n## 测试右移\r\n\r\n### 右移策略\r\n\r\n```text\r\n发布阶段：\r\n├─ 灰度发布：按比例放量\r\n├─ 监控告警：实时监控\r\n├─ 快速回滚：问题时快速回滚\r\n└─ 线上验证：验证发布效果\r\n\r\n线上阶段：\r\n├─ 业务监控：业务指标监控\r\n├─ 技术监控：技术指标监控\r\n├─ 用户反馈：用户问题收集\r\n└─ 混沌工程：主动注入故障\r\n```\r\n\r\n### 右移实践\r\n\r\n```text\r\n实践1：灰度发布\r\n├─ 用户灰度：按用户比例\r\n├─ 流量灰度：按流量比例\r\n├─ 地域灰度：按地域\r\n└─ 监控验证：实时监控\r\n\r\n实践2：线上监控\r\n├─ 业务监控：订单量、成功率\r\n├─ 技术监控：错误率、响应时间\r\n├─ 资源监控：CPU、内存、磁盘\r\n└─ 告警通知：异常告警\r\n\r\n实践3：混沌工程\r\n├─ 故障注入：模拟故障\r\n├─ 韧性验证：验证系统韧性\r\n├─ 恢复测试：验证恢复能力\r\n└─ 改进优化：持续改进\r\n```\r\n\r\n## CI/CD 流水线设计\r\n\r\n### 流水线阶段\r\n\r\n```text\r\n代码提交 → 代码检查 → 单元测试 → 接口测试 → 集成测试 → 部署 → 冒烟测试 → 灰度发布 → 全量发布\r\n\r\n各阶段职责：\r\n├─ 代码提交：提交代码\r\n├─ 代码检查：静态代码分析\r\n├─ 单元测试：执行单元测试\r\n├─ 接口测试：执行接口测试\r\n├─ 集成测试：执行集成测试\r\n├─ 部署：部署到测试环境\r\n├─ 冒烟测试：执行冒烟测试\r\n├─ 灰度发布：按比例发布\r\n└─ 全量发布：全量发布\r\n```\r\n\r\n### 质量门禁\r\n\r\n```text\r\n门禁标准：\r\n├─ 代码检查\r\n│   ├─ 代码规范：无严重违规\r\n│   ├─ 代码重复：< 5%\r\n│   └─ 圈复杂度：< 10\r\n│\r\n├─ 单元测试\r\n│   ├─ 覆盖率：≥ 80%\r\n│   ├─ 通过率：100%\r\n│   └─ 执行时间：< 5分钟\r\n│\r\n├─ 接口测试\r\n│   ├─ 覆盖率：≥ 90%\r\n│   ├─ 通过率：100%\r\n│   └─ 执行时间：< 10分钟\r\n│\r\n├─ 集成测试\r\n│   ├─ 通过率：100%\r\n│   └─ 执行时间：< 30分钟\r\n│\r\n└─ 冒烟测试\r\n    ├─ 通过率：100%\r\n    └─ 核心功能：全部通过\r\n```\r\n\r\n### 工具选型\r\n\r\n```text\r\n├─ 代码管理\r\n│   ├─ Git：版本控制\r\n│   └─ GitLab/GitHub：代码托管\r\n│\r\n├─ CI/CD工具\r\n│   ├─ Jenkins：开源、灵活\r\n│   ├─ GitLab CI：集成度高\r\n│   ├─ GitHub Actions：云端友好\r\n│   └─ CircleCI：云端CI\r\n│\r\n├─ 测试工具\r\n│   ├─ JUnit/TestNG：单元测试\r\n│   ├─ Pytest：Python测试\r\n│   ├─ Postman/Newman：接口测试\r\n│   └─ Selenium/Playwright：UI测试\r\n│\r\n└─ 报告工具\r\n    ├─ Allure：测试报告\r\n    ├─ SonarQube：代码质量\r\n    └─ Grafana：监控可视化\r\n```\r\n\r\n## 输出示例\r\n\r\n**团队需要将测试接入CI/CD流水线**\r\n→ 设计流水线阶段：提交触发→单元测试→接口测试→UI测试→质量门禁→报告\r\n→ 左移：需求阶段定义验收标准，开发阶段推动单元测试\r\n→ 右移：灰度发布监控指标，线上质量监控告警\r\n\r\n**现有CI/CD测试效率低下（跑一次1小时）**\r\n→ 优化策略：分层并行执行、增量测试、智能用例筛选\r\n\r\n## 检查清单\r\n\r\n持续测试实践完成后检查：\r\n- [ ] 测试左移是否实施？\r\n- [ ] 测试右移是否规划？\r\n- [ ] CI/CD流水线是否设计？\r\n- [ ] 质量门禁是否定义？\r\n- [ ] 工具选型是否完成？\r\n- [ ] 监控告警是否配置？\n\nFile v1.7.6:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-ci-cd-testing\",\n  \"version\": \"1.7.6\",\n  \"publishedAt\": 1788266266224\n}\n\nFile v1.7.6:skill-card.md\n\n## Description:\n\nHelps developers, QA engineers, and DevOps teams design layered CI/CD testing stages, quality gates, and feedback loops.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, QA engineers, and DevOps teams use this skill when they need to integrate testing into CI/CD pipelines, structure test stages, set quality gates, and improve automated regression feedback.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The security summary flags guidance to run an unpinned remote installer for a broader skill set.\n\nMitigation: Review the referenced `Kokxi/qa-test-skills` source and install only with a pinned, trusted installer and immutable commit or release.\n\nRisk: Generated CI/CD, deployment, or production commands could affect release environments if run without review.\n\nMitigation: Treat outputs as documentation until a human confirms authorization, pipeline changes, rollback planning, and production impact.\n\n## Reference(s):\n\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Configuration, Shell commands, Guidance]\n\n**Output Format:** [Markdown with structured tables, pipeline guidance, and inline command examples]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include PIPE-XXXX traceability identifiers, nine-column test case tables, CI/CD stage designs, quality gates, and feedback loop recommendations.]\n\n## Skill Version(s):\n\n1.7.6 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.7.5: 3 files, 4934 bytes\n\nFiles: skill-card.md (1845b), SKILL.md (8079b), _meta.json (135b)\n\nFile v1.7.5:SKILL.md\n\n---\nname: qa-ci-cd-testing\nslug: qa-ci-cd-testing\ndisplayName: Ci Cd Testing\nversion: 1.7.5\ndescription: >-\n  当需要把测试集成到 CI/CD 流水线中、或者现有流水线的测试环节跑起来效率低不可靠时使用此技能。覆盖流水线各阶段的分层测试卡点设计（提交检查→单元测试→接口测试→UI 测试→回归测试）、工具集成策略和质量门禁配置。不要在 CI 里堆满慢的 UI 测试——而是构建测试金字塔：提交阶段跑最快的（<5min），合码阶段跑核心的（<15min），夜间跑全量的。\n\nwhen_to_use: 用户说\"CI/CD\"、\"持续测试\"、\"流水线测试\"、\"质量门禁\"、\"自动化回归\"、\"提交即测试\"、需要设计CI/CD测试流程、构建流水线需要加入测试环节时\nallowed-tools: Read Grep Glob Bash\nrelated_skills:\n  upstream:\n    - qa-tech-selection          # 输入：技术选型确定工具栈\n    - qa-test-strategy-design    # 输入：测试策略确定自动化范围\n  downstream:\n    - qa-release-risk-governance # 输出：CI/CD流程支持发布\n    - qa-shift-right\ninput_format:\n  required:\n    - name: 测试策略\n      type: object\n      description: 来自qa-test-strategy-design的测试策略\n    - name: 自动化架构\n      type: object\n      description: 来自qa-test-automation-arch的自动化架构\n  optional:\n    - name: 流水线配置\n      type: string\n      description: CI/CD流水线配置信息\noutput_format:\n  traceability:\n    - 每条流水线带唯一ID（PIPE-XXXX）\n  structure:\n    - 测试用例表格：固定 9 列（用例编号|测试类型|功能模块|测试标题|用例级别|预置条件|测试步骤|预期结果|风险等级）\n    - 用例级别：P0≤20%（核心流程）/ P1≤40%（主要功能）/ P2≤30%（次要功能）/ P3≤10%（边缘场景）\n    - 覆盖率：标注口径（基于现有需求/输入文档），禁止\"全覆盖/100%\"绝对化表述；缺失模块标注\"未覆盖+原因\"\n    - pipeline_design: CI/CD流水线设计\n    - test_stages: 各阶段测试配置\n    - quality_gates: 质量门禁设置\n    - feedback_loops: 反馈循环机制\ncategories: ['Development','Testing','DevOps']\ndepth_requirement_quantification:\n  reference_value: \"根据流水线复杂度调整设计深度：简单×1/中等×2/复杂×3\"\n  minimum: \"至少覆盖提交检查、接口测试、回归测试3个卡点\"\nerror_recovery_guidance:\n  on_failure: \"流水线测试卡点失败时回退到测试策略调整范围\"\n  retry_behavior: \"调整测试范围或工具后重新配置卡点\"\n---\n> **⚠️ 安全警告**：本技能的示例可能涉及 CI/CD 流水线配置、发布操作和部署环境。\n> 实际使用时请勿在未授权的生产环境执行发布或部署，先确认灰度策略和回滚方案。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 持续测试实践\n\n## 核心原则\n\n测试左移（提前测试）、测试右移（线上验证）、快速反馈。\n\n## 深度要求（参考值）\n\n**关键指标**：根据项目复杂度设计质量门禁策略\n\n| 复杂度 | 流水线阶段 | 质量门禁阈值 | 说明 |\n|--------|-----------|-------------|------|\n| 简单项目 | 2-3个阶段 | 单元测试通过率≥80% | 标准CI流程 |\n| 中等项目 | 4-5个阶段 | 单元≥90%+接口通过率≥95% | 含集成测试 |\n| 复杂项目 | 6-8个阶段 | 全链路≥95%+性能阈值 | 含全量自动化+安全扫描 |\n\n## 测试左移\n\n### 左移策略\n\n```text\n需求阶段：\n├─ 需求评审：测试参与需求评审\n├─ 验收标准：明确验收条件\n├─ 可测试性：评估可测试性\n└─ 测试计划：制定测试计划\n\n开发阶段：\n├─ 代码评审：测试视角的CR\n├─ 单元测试：开发编写单元测试\n├─ 接口测试：测试编写接口测试\n└─ 冒烟测试：开发自测通过\n\n集成阶段：\n├─ 接口自动化：自动执行接口测试\n├─ 集成测试：自动执行集成测试\n└─ 冒烟测试：自动执行冒烟测试\n```\n\n### 左移实践\n\n```text\n实践1：需求可测试性评估\n├─ 验收条件是否明确？\n├─ 是否可自动化验证？\n├─ 测试数据是否可准备？\n└─ 测试环境是否可搭建？\n\n实践2：代码评审检查点\n├─ 业务逻辑是否正确？\n├─ 异常处理是否完善？\n├─ 日志记录是否完整？\n└─ 测试代码是否同步？\n\n实践3：单元测试覆盖\n├─ 核心逻辑单元测试\n├─ 分支覆盖\n├─ 边界覆盖\n└─ 异常覆盖\n```\n\n## 测试右移\n\n### 右移策略\n\n```text\n发布阶段：\n├─ 灰度发布：按比例放量\n├─ 监控告警：实时监控\n├─ 快速回滚：问题时快速回滚\n└─ 线上验证：验证发布效果\n\n线上阶段：\n├─ 业务监控：业务指标监控\n├─ 技术监控：技术指标监控\n├─ 用户反馈：用户问题收集\n└─ 混沌工程：主动注入故障\n```\n\n### 右移实践\n\n```text\n实践1：灰度发布\n├─ 用户灰度：按用户比例\n├─ 流量灰度：按流量比例\n├─ 地域灰度：按地域\n└─ 监控验证：实时监控\n\n实践2：线上监控\n├─ 业务监控：订单量、成功率\n├─ 技术监控：错误率、响应时间\n├─ 资源监控：CPU、内存、磁盘\n└─ 告警通知：异常告警\n\n实践3：混沌工程\n├─ 故障注入：模拟故障\n├─ 韧性验证：验证系统韧性\n├─ 恢复测试：验证恢复能力\n└─ 改进优化：持续改进\n```\n\n## CI/CD 流水线设计\n\n### 流水线阶段\n\n```text\n代码提交 → 代码检查 → 单元测试 → 接口测试 → 集成测试 → 部署 → 冒烟测试 → 灰度发布 → 全量发布\n\n各阶段职责：\n├─ 代码提交：提交代码\n├─ 代码检查：静态代码分析\n├─ 单元测试：执行单元测试\n├─ 接口测试：执行接口测试\n├─ 集成测试：执行集成测试\n├─ 部署：部署到测试环境\n├─ 冒烟测试：执行冒烟测试\n├─ 灰度发布：按比例发布\n└─ 全量发布：全量发布\n```\n\n### 质量门禁\n\n```text\n门禁标准：\n├─ 代码检查\n│   ├─ 代码规范：无严重违规\n│   ├─ 代码重复：< 5%\n│   └─ 圈复杂度：< 10\n│\n├─ 单元测试\n│   ├─ 覆盖率：≥ 80%\n│   ├─ 通过率：100%\n│   └─ 执行时间：< 5分钟\n│\n├─ 接口测试\n│   ├─ 覆盖率：≥ 90%\n│   ├─ 通过率：100%\n│   └─ 执行时间：< 10分钟\n│\n├─ 集成测试\n│   ├─ 通过率：100%\n│   └─ 执行时间：< 30分钟\n│\n└─ 冒烟测试\n    ├─ 通过率：100%\n    └─ 核心功能：全部通过\n```\n\n### 工具选型\n\n```text\n├─ 代码管理\n│   ├─ Git：版本控制\n│   └─ GitLab/GitHub：代码托管\n│\n├─ CI/CD工具\n│   ├─ Jenkins：开源、灵活\n│   ├─ GitLab CI：集成度高\n│   ├─ GitHub Actions：云端友好\n│   └─ CircleCI：云端CI\n│\n├─ 测试工具\n│   ├─ JUnit/TestNG：单元测试\n│   ├─ Pytest：Python测试\n│   ├─ Postman/Newman：接口测试\n│   └─ Selenium/Playwright：UI测试\n│\n└─ 报告工具\n    ├─ Allure：测试报告\n    ├─ SonarQube：代码质量\n    └─ Grafana：监控可视化\n```\n\n## 输出示例\n\n**团队需要将测试接入CI/CD流水线**\n→ 设计流水线阶段：提交触发→单元测试→接口测试→UI测试→质量门禁→报告\n→ 左移：需求阶段定义验收标准，开发阶段推动单元测试\n→ 右移：灰度发布监控指标，线上质量监控告警\n\n**现有CI/CD测试效率低下（跑一次1小时）**\n→ 优化策略：分层并行执行、增量测试、智能用例筛选\n\n## 检查清单\n\n持续测试实践完成后检查：\n- [ ] 测试左移是否实施？\n- [ ] 测试右移是否规划？\n- [ ] CI/CD流水线是否设计？\n- [ ] 质量门禁是否定义？\n- [ ] 工具选型是否完成？\n- [ ] 监控告警是否配置？\n\nFile v1.7.5:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-ci-cd-testing\",\n  \"version\": \"1.7.5\",\n  \"publishedAt\": 1788102736075\n}\n\nFile v1.7.5:skill-card.md\n\n## Description:\n\nProvides Chinese-language guidance for integrating layered testing into CI/CD pipelines, including staged test checkpoints, tool integration, and quality-gate configuration.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, QA engineers, and DevOps teams use this skill to design continuous-testing workflows, quality gates, and feedback loops for CI/CD pipelines. It is intended for Chinese-language guidance on layered pipeline testing rather than direct deployment execution.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Pipeline or release guidance could be applied to production environments without adequate authorization, gray-release planning, or rollback preparation.\n\nMitigation: Review generated pipeline and deployment suggestions before use, confirm authorization, and validate gray-release and rollback plans before production changes.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/kokxi/skills/qa-ci-cd-testing)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Configuration, Guidance]\n\n**Output Format:** [Markdown guidance with structured tables and CI/CD pipeline sections]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Pipeline entries may use PIPE-XXXX traceability IDs; generated test-case tables follow the skill's fixed nine-column structure when applicable.]\n\n## Skill Version(s):\n\n1.7.5 (source: frontmatter and server evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.6.3: 3 files, 4571 bytes\n\nFiles: skill-card.md (1603b), SKILL.md (7638b), _meta.json (135b)\n\nFile v1.6.3:SKILL.md\n\n---\nname: qa-ci-cd-testing\nslug: qa-ci-cd-testing\ndisplayName: Ci Cd Testing\nversion: 1.6.3\ndescription: >-\n  当需要把测试集成到 CI/CD 流水线中、或者现有流水线的测试环节跑起来效率低不可靠时使用此技能。覆盖流水线各阶段的分层测试卡点设计（提交检查→单元测试→接口测试→UI 测试→回归测试）、工具集成策略和质量门禁配置。不要在 CI 里堆满慢的 UI 测试——而是构建测试金字塔：提交阶段跑最快的（<5min），合码阶段跑核心的（<15min），夜间跑全量的。\n\nwhen_to_use: 用户说\"CI/CD\"、\"持续测试\"、\"流水线测试\"、\"质量门禁\"、\"自动化回归\"、\"提交即测试\"、需要设计CI/CD测试流程、构建流水线需要加入测试环节时\nallowed-tools: Read Grep Glob Bash\nrelated_skills:\n  upstream:\n    - qa-tech-selection          # 输入：技术选型确定工具栈\n    - qa-test-strategy-design    # 输入：测试策略确定自动化范围\n  downstream:\n    - qa-release-risk-governance # 输出：CI/CD流程支持发布\n    - qa-shift-right\ninput_format:\n  required:\n    - name: 测试策略\n      type: object\n      description: 来自qa-test-strategy-design的测试策略\n    - name: 自动化架构\n      type: object\n      description: 来自qa-test-automation-arch的自动化架构\n  optional:\n    - name: 流水线配置\n      type: string\n      description: CI/CD流水线配置信息\noutput_format:\n  traceability:\n    - 每条流水线带唯一ID（PIPE-XXXX）\n  structure:\n    - pipeline_design: CI/CD流水线设计\n    - test_stages: 各阶段测试配置\n    - quality_gates: 质量门禁设置\n    - feedback_loops: 反馈循环机制\ncategories: ['Development','Testing','DevOps']\ndepth_requirement_quantification:\n  reference_value: \"根据流水线复杂度调整设计深度：简单×1/中等×2/复杂×3\"\n  minimum: \"至少覆盖提交检查、接口测试、回归测试3个卡点\"\nerror_recovery_guidance:\n  on_failure: \"流水线测试卡点失败时回退到测试策略调整范围\"\n  retry_behavior: \"调整测试范围或工具后重新配置卡点\"\n---\n> **⚠️ 安全警告**：本技能的示例可能涉及 CI/CD 流水线配置、发布操作和部署环境。\n> 实际使用时请勿在未授权的生产环境执行发布或部署，先确认灰度策略和回滚方案。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 持续测试实践\n\n## 核心原则\n\n测试左移（提前测试）、测试右移（线上验证）、快速反馈。\n\n## 深度要求（参考值）\n\n**关键指标**：根据项目复杂度设计质量门禁策略\n\n| 复杂度 | 流水线阶段 | 质量门禁阈值 | 说明 |\n|--------|-----------|-------------|------|\n| 简单项目 | 2-3个阶段 | 单元测试通过率≥80% | 标准CI流程 |\n| 中等项目 | 4-5个阶段 | 单元≥90%+接口通过率≥95% | 含集成测试 |\n| 复杂项目 | 6-8个阶段 | 全链路≥95%+性能阈值 | 含全量自动化+安全扫描 |\n\n## 测试左移\n\n### 左移策略\n\n```text\n需求阶段：\n├─ 需求评审：测试参与需求评审\n├─ 验收标准：明确验收条件\n├─ 可测试性：评估可测试性\n└─ 测试计划：制定测试计划\n\n开发阶段：\n├─ 代码评审：测试视角的CR\n├─ 单元测试：开发编写单元测试\n├─ 接口测试：测试编写接口测试\n└─ 冒烟测试：开发自测通过\n\n集成阶段：\n├─ 接口自动化：自动执行接口测试\n├─ 集成测试：自动执行集成测试\n└─ 冒烟测试：自动执行冒烟测试\n```\n\n### 左移实践\n\n```text\n实践1：需求可测试性评估\n├─ 验收条件是否明确？\n├─ 是否可自动化验证？\n├─ 测试数据是否可准备？\n└─ 测试环境是否可搭建？\n\n实践2：代码评审检查点\n├─ 业务逻辑是否正确？\n├─ 异常处理是否完善？\n├─ 日志记录是否完整？\n└─ 测试代码是否同步？\n\n实践3：单元测试覆盖\n├─ 核心逻辑单元测试\n├─ 分支覆盖\n├─ 边界覆盖\n└─ 异常覆盖\n```\n\n## 测试右移\n\n### 右移策略\n\n```text\n发布阶段：\n├─ 灰度发布：按比例放量\n├─ 监控告警：实时监控\n├─ 快速回滚：问题时快速回滚\n└─ 线上验证：验证发布效果\n\n线上阶段：\n├─ 业务监控：业务指标监控\n├─ 技术监控：技术指标监控\n├─ 用户反馈：用户问题收集\n└─ 混沌工程：主动注入故障\n```\n\n### 右移实践\n\n```text\n实践1：灰度发布\n├─ 用户灰度：按用户比例\n├─ 流量灰度：按流量比例\n├─ 地域灰度：按地域\n└─ 监控验证：实时监控\n\n实践2：线上监控\n├─ 业务监控：订单量、成功率\n├─ 技术监控：错误率、响应时间\n├─ 资源监控：CPU、内存、磁盘\n└─ 告警通知：异常告警\n\n实践3：混沌工程\n├─ 故障注入：模拟故障\n├─ 韧性验证：验证系统韧性\n├─ 恢复测试：验证恢复能力\n└─ 改进优化：持续改进\n```\n\n## CI/CD 流水线设计\n\n### 流水线阶段\n\n```text\n代码提交 → 代码检查 → 单元测试 → 接口测试 → 集成测试 → 部署 → 冒烟测试 → 灰度发布 → 全量发布\n\n各阶段职责：\n├─ 代码提交：提交代码\n├─ 代码检查：静态代码分析\n├─ 单元测试：执行单元测试\n├─ 接口测试：执行接口测试\n├─ 集成测试：执行集成测试\n├─ 部署：部署到测试环境\n├─ 冒烟测试：执行冒烟测试\n├─ 灰度发布：按比例发布\n└─ 全量发布：全量发布\n```\n\n### 质量门禁\n\n```text\n门禁标准：\n├─ 代码检查\n│   ├─ 代码规范：无严重违规\n│   ├─ 代码重复：< 5%\n│   └─ 圈复杂度：< 10\n│\n├─ 单元测试\n│   ├─ 覆盖率：≥ 80%\n│   ├─ 通过率：100%\n│   └─ 执行时间：< 5分钟\n│\n├─ 接口测试\n│   ├─ 覆盖率：≥ 90%\n│   ├─ 通过率：100%\n│   └─ 执行时间：< 10分钟\n│\n├─ 集成测试\n│   ├─ 通过率：100%\n│   └─ 执行时间：< 30分钟\n│\n└─ 冒烟测试\n    ├─ 通过率：100%\n    └─ 核心功能：全部通过\n```\n\n### 工具选型\n\n```text\n├─ 代码管理\n│   ├─ Git：版本控制\n│   └─ GitLab/GitHub：代码托管\n│\n├─ CI/CD工具\n│   ├─ Jenkins：开源、灵活\n│   ├─ GitLab CI：集成度高\n│   ├─ GitHub Actions：云端友好\n│   └─ CircleCI：云端CI\n│\n├─ 测试工具\n│   ├─ JUnit/TestNG：单元测试\n│   ├─ Pytest：Python测试\n│   ├─ Postman/Newman：接口测试\n│   └─ Selenium/Playwright：UI测试\n│\n└─ 报告工具\n    ├─ Allure：测试报告\n    ├─ SonarQube：代码质量\n    └─ Grafana：监控可视化\n```\n\n## 输出示例\n\n**团队需要将测试接入CI/CD流水线**\n→ 设计流水线阶段：提交触发→单元测试→接口测试→UI测试→质量门禁→报告\n→ 左移：需求阶段定义验收标准，开发阶段推动单元测试\n→ 右移：灰度发布监控指标，线上质量监控告警\n\n**现有CI/CD测试效率低下（跑一次1小时）**\n→ 优化策略：分层并行执行、增量测试、智能用例筛选\n\n## 检查清单\n\n持续测试实践完成后检查：\n- [ ] 测试左移是否实施？\n- [ ] 测试右移是否规划？\n- [ ] CI/CD流水线是否设计？\n- [ ] 质量门禁是否定义？\n- [ ] 工具选型是否完成？\n- [ ] 监控告警是否配置？\n\nFile v1.6.3:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-ci-cd-testing\",\n  \"version\": \"1.6.3\",\n  \"publishedAt\": 1786548125180\n}\n\nFile v1.6.3:skill-card.md\n\n## Description:\n\nHelps teams design continuous testing for CI/CD pipelines, including staged test gates, tool integration strategies, and quality gate configuration.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, QA engineers, and DevOps teams use this skill to add effective test stages to CI/CD pipelines, define quality gates, and improve feedback speed without overloading pipelines with slow UI tests.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: CI/CD and deployment examples may lead to unintended release, deployment, or production-setting changes if run without review.\n\nMitigation: Review generated pipeline guidance and commands before execution, confirm authorization, and verify rollback or canary strategy before applying changes.\n\n## Reference(s):\n\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Configuration instructions, Markdown]\n\n**Output Format:** [Markdown guidance with structured CI/CD testing recommendations]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May describe pipeline IDs, test stages, quality gates, and feedback loops.]\n\n## Skill Version(s):\n\n1.6.3 (source: server release evidence and SKILL.md frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.6.0: 3 files, 4760 bytes\n\nFiles: skill-card.md (2064b), SKILL.md (7827b), _meta.json (135b)\n\nFile v1.6.0:SKILL.md\n\n---\r\nname: qa-ci-cd-testing\r\nversion: 1.6.0\r\ndescription: >-\r\n  当需要把测试集成到 CI/CD 流水线中、或者现有流水线的测试环节跑起来效率低不可靠时使用此技能。覆盖流水线各阶段的分层测试卡点设计（提交检查→单元测试→接口测试→UI 测试→回归测试）、工具集成策略和质量门禁配置。不要在 CI 里堆满慢的 UI 测试——而是构建测试金字塔：提交阶段跑最快的（<5min），合码阶段跑核心的（<15min），夜间跑全量的。\r\n\r\nwhen_to_use: 用户说\"CI/CD\"、\"持续测试\"、\"流水线测试\"、\"质量门禁\"、\"自动化回归\"、\"提交即测试\"、需要设计CI/CD测试流程、构建流水线需要加入测试环节时\r\nallowed-tools: Read Grep Glob Bash\r\nrelated_skills:\r\n  upstream:\r\n    - qa-tech-selection          # 输入：技术选型确定工具栈\r\n    - qa-test-strategy-design    # 输入：测试策略确定自动化范围\r\n  downstream:\r\n    - qa-release-risk-governance # 输出：CI/CD流程支持发布\r\n    - qa-shift-right\r\ninput_format:\r\n  required:\r\n    - name: 测试策略\r\n      type: object\r\n      description: 来自qa-test-strategy-design的测试策略\r\n    - name: 自动化架构\r\n      type: object\r\n      description: 来自qa-test-automation-arch的自动化架构\r\n  optional:\r\n    - name: 流水线配置\r\n      type: string\r\n      description: CI/CD流水线配置信息\r\noutput_format:\r\n  traceability:\r\n    - 每条流水线带唯一ID（PIPE-XXXX）\r\n  structure:\r\n    - pipeline_design: CI/CD流水线设计\r\n    - test_stages: 各阶段测试配置\r\n    - quality_gates: 质量门禁设置\r\n    - feedback_loops: 反馈循环机制\r\ncategories: ['Development','Testing','DevOps']\r\ndepth_requirement_quantification:\r\n  reference_value: \"根据流水线复杂度调整设计深度：简单×1/中等×2/复杂×3\"\r\n  minimum: \"至少覆盖提交检查、接口测试、回归测试3个卡点\"\r\nerror_recovery_guidance:\r\n  on_failure: \"流水线测试卡点失败时回退到测试策略调整范围\"\r\n  retry_behavior: \"调整测试范围或工具后重新配置卡点\"\r\n---\r\n> **⚠️ 安全警告**：本技能的示例可能涉及 CI/CD 流水线配置、发布操作和部署环境。\r\n> 实际使用时请勿在未授权的生产环境执行发布或部署，先确认灰度策略和回滚方案。\r\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\r\n\r\n# 持续测试实践\r\n\r\n## 核心原则\r\n\r\n测试左移（提前测试）、测试右移（线上验证）、快速反馈。\r\n\r\n## 深度要求（参考值）\r\n\r\n**关键指标**：根据项目复杂度设计质量门禁策略\r\n\r\n| 复杂度 | 流水线阶段 | 质量门禁阈值 | 说明 |\r\n|--------|-----------|-------------|------|\r\n| 简单项目 | 2-3个阶段 | 单元测试通过率≥80% | 标准CI流程 |\r\n| 中等项目 | 4-5个阶段 | 单元≥90%+接口通过率≥95% | 含集成测试 |\r\n| 复杂项目 | 6-8个阶段 | 全链路≥95%+性能阈值 | 含全量自动化+安全扫描 |\r\n\r\n## 测试左移\r\n\r\n### 左移策略\r\n\r\n```text\r\n需求阶段：\r\n├─ 需求评审：测试参与需求评审\r\n├─ 验收标准：明确验收条件\r\n├─ 可测试性：评估可测试性\r\n└─ 测试计划：制定测试计划\r\n\r\n开发阶段：\r\n├─ 代码评审：测试视角的CR\r\n├─ 单元测试：开发编写单元测试\r\n├─ 接口测试：测试编写接口测试\r\n└─ 冒烟测试：开发自测通过\r\n\r\n集成阶段：\r\n├─ 接口自动化：自动执行接口测试\r\n├─ 集成测试：自动执行集成测试\r\n└─ 冒烟测试：自动执行冒烟测试\r\n```\r\n\r\n### 左移实践\r\n\r\n```text\r\n实践1：需求可测试性评估\r\n├─ 验收条件是否明确？\r\n├─ 是否可自动化验证？\r\n├─ 测试数据是否可准备？\r\n└─ 测试环境是否可搭建？\r\n\r\n实践2：代码评审检查点\r\n├─ 业务逻辑是否正确？\r\n├─ 异常处理是否完善？\r\n├─ 日志记录是否完整？\r\n└─ 测试代码是否同步？\r\n\r\n实践3：单元测试覆盖\r\n├─ 核心逻辑单元测试\r\n├─ 分支覆盖\r\n├─ 边界覆盖\r\n└─ 异常覆盖\r\n```\r\n\r\n## 测试右移\r\n\r\n### 右移策略\r\n\r\n```text\r\n发布阶段：\r\n├─ 灰度发布：按比例放量\r\n├─ 监控告警：实时监控\r\n├─ 快速回滚：问题时快速回滚\r\n└─ 线上验证：验证发布效果\r\n\r\n线上阶段：\r\n├─ 业务监控：业务指标监控\r\n├─ 技术监控：技术指标监控\r\n├─ 用户反馈：用户问题收集\r\n└─ 混沌工程：主动注入故障\r\n```\r\n\r\n### 右移实践\r\n\r\n```text\r\n实践1：灰度发布\r\n├─ 用户灰度：按用户比例\r\n├─ 流量灰度：按流量比例\r\n├─ 地域灰度：按地域\r\n└─ 监控验证：实时监控\r\n\r\n实践2：线上监控\r\n├─ 业务监控：订单量、成功率\r\n├─ 技术监控：错误率、响应时间\r\n├─ 资源监控：CPU、内存、磁盘\r\n└─ 告警通知：异常告警\r\n\r\n实践3：混沌工程\r\n├─ 故障注入：模拟故障\r\n├─ 韧性验证：验证系统韧性\r\n├─ 恢复测试：验证恢复能力\r\n└─ 改进优化：持续改进\r\n```\r\n\r\n## CI/CD 流水线设计\r\n\r\n### 流水线阶段\r\n\r\n```text\r\n代码提交 → 代码检查 → 单元测试 → 接口测试 → 集成测试 → 部署 → 冒烟测试 → 灰度发布 → 全量发布\r\n\r\n各阶段职责：\r\n├─ 代码提交：提交代码\r\n├─ 代码检查：静态代码分析\r\n├─ 单元测试：执行单元测试\r\n├─ 接口测试：执行接口测试\r\n├─ 集成测试：执行集成测试\r\n├─ 部署：部署到测试环境\r\n├─ 冒烟测试：执行冒烟测试\r\n├─ 灰度发布：按比例发布\r\n└─ 全量发布：全量发布\r\n```\r\n\r\n### 质量门禁\r\n\r\n```text\r\n门禁标准：\r\n├─ 代码检查\r\n│   ├─ 代码规范：无严重违规\r\n│   ├─ 代码重复：< 5%\r\n│   └─ 圈复杂度：< 10\r\n│\r\n├─ 单元测试\r\n│   ├─ 覆盖率：≥ 80%\r\n│   ├─ 通过率：100%\r\n│   └─ 执行时间：< 5分钟\r\n│\r\n├─ 接口测试\r\n│   ├─ 覆盖率：≥ 90%\r\n│   ├─ 通过率：100%\r\n│   └─ 执行时间：< 10分钟\r\n│\r\n├─ 集成测试\r\n│   ├─ 通过率：100%\r\n│   └─ 执行时间：< 30分钟\r\n│\r\n└─ 冒烟测试\r\n    ├─ 通过率：100%\r\n    └─ 核心功能：全部通过\r\n```\r\n\r\n### 工具选型\r\n\r\n```text\r\n├─ 代码管理\r\n│   ├─ Git：版本控制\r\n│   └─ GitLab/GitHub：代码托管\r\n│\r\n├─ CI/CD工具\r\n│   ├─ Jenkins：开源、灵活\r\n│   ├─ GitLab CI：集成度高\r\n│   ├─ GitHub Actions：云端友好\r\n│   └─ CircleCI：云端CI\r\n│\r\n├─ 测试工具\r\n│   ├─ JUnit/TestNG：单元测试\r\n│   ├─ Pytest：Python测试\r\n│   ├─ Postman/Newman：接口测试\r\n│   └─ Selenium/Playwright：UI测试\r\n│\r\n└─ 报告工具\r\n    ├─ Allure：测试报告\r\n    ├─ SonarQube：代码质量\r\n    └─ Grafana：监控可视化\r\n```\r\n\r\n## 输出示例\r\n\r\n**团队需要将测试接入CI/CD流水线**\r\n→ 设计流水线阶段：提交触发→单元测试→接口测试→UI测试→质量门禁→报告\r\n→ 左移：需求阶段定义验收标准，开发阶段推动单元测试\r\n→ 右移：灰度发布监控指标，线上质量监控告警\r\n\r\n**现有CI/CD测试效率低下（跑一次1小时）**\r\n→ 优化策略：分层并行执行、增量测试、智能用例筛选\r\n\r\n## 检查清单\r\n\r\n持续测试实践完成后检查：\r\n- [ ] 测试左移是否实施？\r\n- [ ] 测试右移是否规划？\r\n- [ ] CI/CD流水线是否设计？\r\n- [ ] 质量门禁是否定义？\r\n- [ ] 工具选型是否完成？\r\n- [ ] 监控告警是否配置？\n\nFile v1.6.0:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-ci-cd-testing\",\n  \"version\": \"1.6.0\",\n  \"publishedAt\": 1783358082953\n}\n\nFile v1.6.0:skill-card.md\n\n## Description: <br>\nProvides CI/CD testing guidance for layered pipeline quality gates, tool integration strategy, and fast feedback across commit checks, unit tests, API tests, UI tests, and regression tests. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[kokxi](https://clawhub.ai/user/kokxi) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers, QA engineers, and DevOps teams use this skill to design CI/CD test stages, define quality gates, and tune feedback loops for reliable automated delivery pipelines. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Pipeline or deployment suggestions may affect production delivery if applied without review. <br>\nMitigation: Review generated CI/CD, deployment, rollback, and quality-gate recommendations before use, especially in production environments. <br>\nRisk: The skill can propose CI/CD testing strategy but does not execute pipelines or validate environment-specific behavior. <br>\nMitigation: Keep execution under explicit user control and validate changes in an authorized workspace or staging environment first. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/kokxi/skills/qa-ci-cd-testing) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, markdown, configuration] <br>\n**Output Format:** [Markdown with structured pipeline design, test-stage, quality-gate, and feedback-loop sections] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Pipeline recommendations include traceability IDs and should be reviewed before applying to production CI/CD systems.] <br>\n\n## Skill Version(s): <br>\n1.6.0 (source: frontmatter and server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.5.0: 3 files, 4415 bytes\n\nFiles: skill-card.md (2234b), SKILL.md (7206b), _meta.json (135b)\n\nFile v1.5.0:SKILL.md\n\n---\r\nname: qa-ci-cd-testing\r\nversion: 1.5.0\r\ndescription: >-\r\n  当需要把测试集成到 CI/CD 流水线中、或者现有流水线的测试环节跑起来效率低不可靠时使用此技能。覆盖流水线各阶段的分层测试卡点设计（提交检查→单元测试→接口测试→UI 测试→回归测试）、工具集成策略和质量门禁配置。不要在 CI 里堆满慢的 UI 测试——而是构建测试金字塔：提交阶段跑最快的（<5min），合码阶段跑核心的（<15min），夜间跑全量的。\r\n\r\nwhen_to_use: 用户说\"CI/CD\"、\"持续测试\"、\"自动化测试\"、\"流水线\"、\"质量门禁\"、\"自动化回归\"、\"提交即测试\"、\"左移\"、\"右移\"、需要设计CI/CD测试流程、构建流水线需要加入测试环节时\r\nallowed-tools: Read Grep Glob Bash\r\nrelated_skills:\r\n  upstream:\r\n    - qa-tech-selection          # 输入：技术选型确定工具栈\r\n    - qa-test-strategy-design    # 输入：测试策略确定自动化范围\r\n  downstream:\r\n    - qa-release-risk-governance # 输出：CI/CD流程支持发布\r\ninput_format:\r\n  required:\r\n    - name: 测试策略\r\n      type: object\r\n      description: 来自qa-test-strategy-design的测试策略\r\n    - name: 自动化架构\r\n      type: object\r\n      description: 来自qa-test-automation-arch的自动化架构\r\n  optional:\r\n    - name: 流水线配置\r\n      type: string\r\n      description: CI/CD流水线配置信息\r\noutput_format:\r\n  structure:\r\n    - pipeline_design: CI/CD流水线设计\r\n    - test_stages: 各阶段测试配置\r\n    - quality_gates: 质量门禁设置\r\n    - feedback_loops: 反馈循环机制\r\n---\r\n\r\n# 持续测试实践\r\n\r\n## 核心原则\r\n\r\n你是一位持续测试专家，擅长将测试集成到CI/CD流程中。\r\n**核心原则**：测试左移（提前测试）、测试右移（线上验证）、快速反馈。\r\n本技能覆盖流水线设计、质量门禁、工具集成和监控告警的全流程方案。\r\n\r\n## 深度要求（参考值）\r\n\r\n**关键指标**：根据项目复杂度设计质量门禁策略\r\n\r\n| 复杂度 | 流水线阶段 | 质量门禁阈值 | 说明 |\r\n|--------|-----------|-------------|------|\r\n| 简单项目 | 2-3个阶段 | 单元测试通过率≥80% | 标准CI流程 |\r\n| 中等项目 | 4-5个阶段 | 单元≥90%+接口通过率≥95% | 含集成测试 |\r\n| 复杂项目 | 6-8个阶段 | 全链路≥95%+性能阈值 | 含全量自动化+安全扫描 |\r\n\r\n## 测试左移\r\n\r\n### 左移策略\r\n\r\n```text\r\n需求阶段：\r\n├─ 需求评审：测试参与需求评审\r\n├─ 验收标准：明确验收条件\r\n├─ 可测试性：评估可测试性\r\n└─ 测试计划：制定测试计划\r\n\r\n开发阶段：\r\n├─ 代码评审：测试视角的CR\r\n├─ 单元测试：开发编写单元测试\r\n├─ 接口测试：测试编写接口测试\r\n└─ 冒烟测试：开发自测通过\r\n\r\n集成阶段：\r\n├─ 接口自动化：自动执行接口测试\r\n├─ 集成测试：自动执行集成测试\r\n└─ 冒烟测试：自动执行冒烟测试\r\n```\r\n\r\n### 左移实践\r\n\r\n```text\r\n实践1：需求可测试性评估\r\n├─ 验收条件是否明确？\r\n├─ 是否可自动化验证？\r\n├─ 测试数据是否可准备？\r\n└─ 测试环境是否可搭建？\r\n\r\n实践2：代码评审检查点\r\n├─ 业务逻辑是否正确？\r\n├─ 异常处理是否完善？\r\n├─ 日志记录是否完整？\r\n└─ 测试代码是否同步？\r\n\r\n实践3：单元测试覆盖\r\n├─ 核心逻辑单元测试\r\n├─ 分支覆盖\r\n├─ 边界覆盖\r\n└─ 异常覆盖\r\n```\r\n\r\n## 测试右移\r\n\r\n### 右移策略\r\n\r\n```text\r\n发布阶段：\r\n├─ 灰度发布：按比例放量\r\n├─ 监控告警：实时监控\r\n├─ 快速回滚：问题时快速回滚\r\n└─ 线上验证：验证发布效果\r\n\r\n线上阶段：\r\n├─ 业务监控：业务指标监控\r\n├─ 技术监控：技术指标监控\r\n├─ 用户反馈：用户问题收集\r\n└─ 混沌工程：主动注入故障\r\n```\r\n\r\n### 右移实践\r\n\r\n```text\r\n实践1：灰度发布\r\n├─ 用户灰度：按用户比例\r\n├─ 流量灰度：按流量比例\r\n├─ 地域灰度：按地域\r\n└─ 监控验证：实时监控\r\n\r\n实践2：线上监控\r\n├─ 业务监控：订单量、成功率\r\n├─ 技术监控：错误率、响应时间\r\n├─ 资源监控：CPU、内存、磁盘\r\n└─ 告警通知：异常告警\r\n\r\n实践3：混沌工程\r\n├─ 故障注入：模拟故障\r\n├─ 韧性验证：验证系统韧性\r\n├─ 恢复测试：验证恢复能力\r\n└─ 改进优化：持续改进\r\n```\r\n\r\n## CI/CD 流水线设计\r\n\r\n### 流水线阶段\r\n\r\n```text\r\n代码提交 → 代码检查 → 单元测试 → 接口测试 → 集成测试 → 部署 → 冒烟测试 → 灰度发布 → 全量发布\r\n\r\n各阶段职责：\r\n├─ 代码提交：提交代码\r\n├─ 代码检查：静态代码分析\r\n├─ 单元测试：执行单元测试\r\n├─ 接口测试：执行接口测试\r\n├─ 集成测试：执行集成测试\r\n├─ 部署：部署到测试环境\r\n├─ 冒烟测试：执行冒烟测试\r\n├─ 灰度发布：按比例发布\r\n└─ 全量发布：全量发布\r\n```\r\n\r\n### 质量门禁\r\n\r\n```text\r\n门禁标准：\r\n├─ 代码检查\r\n│   ├─ 代码规范：无严重违规\r\n│   ├─ 代码重复：< 5%\r\n│   └─ 圈复杂度：< 10\r\n│\r\n├─ 单元测试\r\n│   ├─ 覆盖率：≥ 80%\r\n│   ├─ 通过率：100%\r\n│   └─ 执行时间：< 5分钟\r\n│\r\n├─ 接口测试\r\n│   ├─ 覆盖率：≥ 90%\r\n│   ├─ 通过率：100%\r\n│   └─ 执行时间：< 10分钟\r\n│\r\n├─ 集成测试\r\n│   ├─ 通过率：100%\r\n│   └─ 执行时间：< 30分钟\r\n│\r\n└─ 冒烟测试\r\n    ├─ 通过率：100%\r\n    └─ 核心功能：全部通过\r\n```\r\n\r\n### 工具选型\r\n\r\n```text\r\n├─ 代码管理\r\n│   ├─ Git：版本控制\r\n│   └─ GitLab/GitHub：代码托管\r\n│\r\n├─ CI/CD工具\r\n│   ├─ Jenkins：开源、灵活\r\n│   ├─ GitLab CI：集成度高\r\n│   ├─ GitHub Actions：云端友好\r\n│   └─ CircleCI：云端CI\r\n│\r\n├─ 测试工具\r\n│   ├─ JUnit/TestNG：单元测试\r\n│   ├─ Pytest：Python测试\r\n│   ├─ Postman/Newman：接口测试\r\n│   └─ Selenium/Playwright：UI测试\r\n│\r\n└─ 报告工具\r\n    ├─ Allure：测试报告\r\n    ├─ SonarQube：代码质量\r\n    └─ Grafana：监控可视化\r\n```\r\n\r\n## 输出示例\r\n\r\n**团队需要将测试接入CI/CD流水线**\r\n→ 设计流水线阶段：提交触发→单元测试→接口测试→UI测试→质量门禁→报告\r\n→ 左移：需求阶段定义验收标准，开发阶段推动单元测试\r\n→ 右移：灰度发布监控指标，线上质量监控告警\r\n\r\n**现有CI/CD测试效率低下（跑一次1小时）**\r\n→ 优化策略：分层并行执行、增量测试、智能用例筛选\r\n\r\n## 检查清单\r\n\r\n持续测试实践完成后检查：\r\n- [ ] 测试左移是否实施？\r\n- [ ] 测试右移是否规划？\r\n- [ ] CI/CD流水线是否设计？\r\n- [ ] 质量门禁是否定义？\r\n- [ ] 工具选型是否完成？\r\n- [ ] 监控告警是否配置？\n\nFile v1.5.0:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-ci-cd-testing\",\n  \"version\": \"1.5.0\",\n  \"publishedAt\": 1782736319599\n}\n\nFile v1.5.0:skill-card.md\n\n## Description: <br>\nProvides Chinese-language guidance for integrating layered automated testing, quality gates, feedback loops, and monitoring into CI/CD pipelines. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[kokxi](https://clawhub.ai/user/kokxi) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers, QA engineers, and release teams use this skill to design CI/CD testing flows, define staged quality gates, and improve feedback speed across commit, merge, regression, and release stages. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may trigger on broad CI/CD or automation-testing mentions when the user does not need pipeline-focused advice. <br>\nMitigation: Confirm the requested workflow needs CI/CD testing or quality-gate guidance before applying the skill. <br>\nRisk: The skill provides Chinese-language guidance that may not match every user's expected working language. <br>\nMitigation: Use it when Chinese output is acceptable, or translate and review recommendations before adoption. <br>\nRisk: Suggested quality-gate thresholds may not fit every project's complexity, risk tolerance, or runtime budget. <br>\nMitigation: Tune thresholds, stage ordering, and runtime targets against project-specific release criteria before deployment. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/kokxi/skills/qa-ci-cd-testing) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, markdown, configuration] <br>\n**Output Format:** [Structured Markdown guidance covering pipeline design, test stages, quality gates, and feedback loops.] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Chinese-language output focused on CI/CD testing practice and quality-gate planning.] <br>\n\n## Skill Version(s): <br>\n1.5.0 (source: frontmatter and server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.4.1: 3 files, 3690 bytes\n\nFiles: skill-card.md (1735b), SKILL.md (5956b), _meta.json (135b)\n\nFile v1.4.1:SKILL.md\n\n---\r\nname: qa-ci-cd-testing\r\ndescription: >-\r\n  持续测试实践，将测试集成到CI/CD流水线实现自动化质量门禁，覆盖流水线设计、工具集成和质量卡点配置。当需要设计或优化CI/CD测试流程时激活。\r\n\r\nwhen_to_use: 用户说\"CI/CD\"、\"持续测试\"、\"自动化测试\"、\"流水线\"、\"质量门禁\"、\"自动化回归\"、\"提交即测试\"、\"左移\"、\"右移\"、需要设计CI/CD测试流程、构建流水线需要加入测试环节时\r\nallowed-tools: Read Grep Glob Bash\r\nrelated_skills:\r\n  upstream:\r\n    - qa-tech-selection          # 输入：技术选型确定工具栈\r\n    - qa-test-strategy-design    # 输入：测试策略确定自动化范围\r\n  downstream:\r\n    - qa-release-risk-governance # 输出：CI/CD流程支持发布\r\ninput_format: 技术选型 + 测试策略\r\noutput_format: CI/CD测试方案（流水线设计+质量门禁+工具集成）\r\n---\r\n\r\n# 持续测试实践\r\n\r\n## Overview\r\n\r\n你是一位持续测试专家，擅长将测试集成到CI/CD流程中。\r\n**核心原则**：测试左移（提前测试）、测试右移（线上验证）、快速反馈。\r\n本技能覆盖流水线设计、质量门禁、工具集成和监控告警的全流程方案。\r\n\r\n## 测试左移\r\n\r\n### 左移策略\r\n\r\n```\r\n需求阶段：\r\n├─ 需求评审：测试参与需求评审\r\n├─ 验收标准：明确验收条件\r\n├─ 可测试性：评估可测试性\r\n└─ 测试计划：制定测试计划\r\n\r\n开发阶段：\r\n├─ 代码评审：测试视角的CR\r\n├─ 单元测试：开发编写单元测试\r\n├─ 接口测试：测试编写接口测试\r\n└─ 冒烟测试：开发自测通过\r\n\r\n集成阶段：\r\n├─ 接口自动化：自动执行接口测试\r\n├─ 集成测试：自动执行集成测试\r\n└─ 冒烟测试：自动执行冒烟测试\r\n```\r\n\r\n### 左移实践\r\n\r\n```\r\n实践1：需求可测试性评估\r\n├─ 验收条件是否明确？\r\n├─ 是否可自动化验证？\r\n├─ 测试数据是否可准备？\r\n└─ 测试环境是否可搭建？\r\n\r\n实践2：代码评审检查点\r\n├─ 业务逻辑是否正确？\r\n├─ 异常处理是否完善？\r\n├─ 日志记录是否完整？\r\n└─ 测试代码是否同步？\r\n\r\n实践3：单元测试覆盖\r\n├─ 核心逻辑单元测试\r\n├─ 分支覆盖\r\n├─ 边界覆盖\r\n└─ 异常覆盖\r\n```\r\n\r\n## 测试右移\r\n\r\n### 右移策略\r\n\r\n```\r\n发布阶段：\r\n├─ 灰度发布：按比例放量\r\n├─ 监控告警：实时监控\r\n├─ 快速回滚：问题时快速回滚\r\n└─ 线上验证：验证发布效果\r\n\r\n线上阶段：\r\n├─ 业务监控：业务指标监控\r\n├─ 技术监控：技术指标监控\r\n├─ 用户反馈：用户问题收集\r\n└─ 混沌工程：主动注入故障\r\n```\r\n\r\n### 右移实践\r\n\r\n```\r\n实践1：灰度发布\r\n├─ 用户灰度：按用户比例\r\n├─ 流量灰度：按流量比例\r\n├─ 地域灰度：按地域\r\n└─ 监控验证：实时监控\r\n\r\n实践2：线上监控\r\n├─ 业务监控：订单量、成功率\r\n├─ 技术监控：错误率、响应时间\r\n├─ 资源监控：CPU、内存、磁盘\r\n└─ 告警通知：异常告警\r\n\r\n实践3：混沌工程\r\n├─ 故障注入：模拟故障\r\n├─ 韧性验证：验证系统韧性\r\n├─ 恢复测试：验证恢复能力\r\n└─ 改进优化：持续改进\r\n```\r\n\r\n## CI/CD 流水线设计\r\n\r\n### 流水线阶段\r\n\r\n```\r\n代码提交 → 代码检查 → 单元测试 → 接口测试 → 集成测试 → 部署 → 冒烟测试 → 灰度发布 → 全量发布\r\n\r\n各阶段职责：\r\n├─ 代码提交：提交代码\r\n├─ 代码检查：静态代码分析\r\n├─ 单元测试：执行单元测试\r\n├─ 接口测试：执行接口测试\r\n├─ 集成测试：执行集成测试\r\n├─ 部署：部署到测试环境\r\n├─ 冒烟测试：执行冒烟测试\r\n├─ 灰度发布：按比例发布\r\n└─ 全量发布：全量发布\r\n```\r\n\r\n### 质量门禁\r\n\r\n```\r\n门禁标准：\r\n├─ 代码检查\r\n│   ├─ 代码规范：无严重违规\r\n│   ├─ 代码重复：< 5%\r\n│   └─ 圈复杂度：< 10\r\n│\r\n├─ 单元测试\r\n│   ├─ 覆盖率：≥ 80%\r\n│   ├─ 通过率：100%\r\n│   └─ 执行时间：< 5分钟\r\n│\r\n├─ 接口测试\r\n│   ├─ 覆盖率：≥ 90%\r\n│   ├─ 通过率：100%\r\n│   └─ 执行时间：< 10分钟\r\n│\r\n├─ 集成测试\r\n│   ├─ 通过率：100%\r\n│   └─ 执行时间：< 30分钟\r\n│\r\n└─ 冒烟测试\r\n    ├─ 通过率：100%\r\n    └─ 核心功能：全部通过\r\n```\r\n\r\n### 工具选型\r\n\r\n```\r\n├─ 代码管理\r\n│   ├─ Git：版本控制\r\n│   └─ GitLab/GitHub：代码托管\r\n│\r\n├─ CI/CD工具\r\n│   ├─ Jenkins：开源、灵活\r\n│   ├─ GitLab CI：集成度高\r\n│   ├─ GitHub Actions：云端友好\r\n│   └─ CircleCI：云端CI\r\n│\r\n├─ 测试工具\r\n│   ├─ JUnit/TestNG：单元测试\r\n│   ├─ Pytest：Python测试\r\n│   ├─ Postman/Newman：接口测试\r\n│   └─ Selenium/Playwright：UI测试\r\n│\r\n└─ 报告工具\r\n    ├─ Allure：测试报告\r\n    ├─ SonarQube：代码质量\r\n    └─ Grafana：监控可视化\r\n```\r\n\r\n## Examples\r\n\r\n**团队需要将测试接入CI/CD流水线**\r\n→ 设计流水线阶段：提交触发→单元测试→接口测试→UI测试→质量门禁→报告\r\n→ 左移：需求阶段定义验收标准，开发阶段推动单元测试\r\n→ 右移：灰度发布监控指标，线上质量监控告警\r\n\r\n**现有CI/CD测试效率低下（跑一次1小时）**\r\n→ 优化策略：分层并行执行、增量测试、智能用例筛选\r\n\r\n## Guidelines\r\n\r\n持续测试实践完成后检查：\r\n- [ ] 测试左移是否实施？\r\n- [ ] 测试右移是否规划？\r\n- [ ] CI/CD流水线是否设计？\r\n- [ ] 质量门禁是否定义？\r\n- [ ] 工具选型是否完成？\r\n- [ ] 监控告警是否配置？\n\nFile v1.4.1:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-ci-cd-testing\",\n  \"version\": \"1.4.1\",\n  \"publishedAt\": 1782406430998\n}\n\nFile v1.4.1:skill-card.md\n\n## Description: <br>\nGuides agents in designing and optimizing CI/CD testing workflows, including continuous testing, pipeline stages, tool integration, quality gates, monitoring, and release validation. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[kokxi](https://clawhub.ai/user/kokxi) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers, QA engineers, and release engineers use this skill to plan CI/CD test integration, automated quality gates, regression feedback loops, and release validation practices. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: CI/CD release changes or chaos-engineering guidance could disrupt production systems if applied without authorization or rollback planning. <br>\nMitigation: Confirm authorization, scope changes narrowly, ensure monitoring is in place, and maintain a tested rollback plan before applying production changes. <br>\n\n\n## Reference(s): <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Guidance, Markdown, Configuration] <br>\n**Output Format:** [Markdown guidance with CI/CD pipeline, quality gate, tool integration, and monitoring recommendations] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [No executable payload; produces advisory testing and release-process guidance.] <br>\n\n## Skill Version(s): <br>\n1.4.1 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.4.0: 3 files, 3893 bytes\n\nFiles: skill-card.md (2105b), SKILL.md (6214b), _meta.json (135b)\n\nFile v1.4.0:SKILL.md\n\n---\r\nname: qa-ci-cd-testing\r\ndescription: >-\r\n  持续测试实践，将测试集成到CI/CD流程中实现自动化质量门禁。当用户需要设计或优化CI/CD测试流程时自动触发。\r\n  也适用于：构建流水线需要加入测试环节、或现有CI/CD测试效率低下需要优化时。\r\n   关键词：CI/CD、持续测试、自动化流水线、质量门禁、测试左移、测试右移、流水线集成、自动化触发、门禁策略、冒烟测试、回归测试、流水线优化。\nwhen_to_use: 用户说\"CI/CD\"、\"持续测试\"、\"自动化测试\"、\"流水线\"、\"质量门禁\"、\"自动化回归\"、\"提交即测试\"、\"左移\"、\"右移\"、需要设计CI/CD测试流程、构建流水线需要加入测试环节时\r\nallowed-tools: Read Grep Glob Bash\r\nrelated_skills:\r\n  upstream:\r\n    - qa-tech-selection          # 输入：技术选型确定工具栈\r\n    - qa-test-strategy-design    # 输入：测试策略确定自动化范围\r\n  downstream:\r\n    - qa-release-risk-governance # 输出：CI/CD流程支持发布\r\ninput_format: 技术选型 + 测试策略\r\noutput_format: CI/CD测试方案（流水线设计+质量门禁+工具集成）\r\n---\r\n\r\n# 持续测试实践\r\n\r\n## Overview\r\n\r\n你是一位持续测试专家，擅长将测试集成到CI/CD流程中。\r\n**核心原则**：测试左移（提前测试）、测试右移（线上验证）、快速反馈。\r\n本技能覆盖流水线设计、质量门禁、工具集成和监控告警的全流程方案。\r\n\r\n## 测试左移\r\n\r\n### 左移策略\r\n\r\n```\r\n需求阶段：\r\n├─ 需求评审：测试参与需求评审\r\n├─ 验收标准：明确验收条件\r\n├─ 可测试性：评估可测试性\r\n└─ 测试计划：制定测试计划\r\n\r\n开发阶段：\r\n├─ 代码评审：测试视角的CR\r\n├─ 单元测试：开发编写单元测试\r\n├─ 接口测试：测试编写接口测试\r\n└─ 冒烟测试：开发自测通过\r\n\r\n集成阶段：\r\n├─ 接口自动化：自动执行接口测试\r\n├─ 集成测试：自动执行集成测试\r\n└─ 冒烟测试：自动执行冒烟测试\r\n```\r\n\r\n### 左移实践\r\n\r\n```\r\n实践1：需求可测试性评估\r\n├─ 验收条件是否明确？\r\n├─ 是否可自动化验证？\r\n├─ 测试数据是否可准备？\r\n└─ 测试环境是否可搭建？\r\n\r\n实践2：代码评审检查点\r\n├─ 业务逻辑是否正确？\r\n├─ 异常处理是否完善？\r\n├─ 日志记录是否完整？\r\n└─ 测试代码是否同步？\r\n\r\n实践3：单元测试覆盖\r\n├─ 核心逻辑单元测试\r\n├─ 分支覆盖\r\n├─ 边界覆盖\r\n└─ 异常覆盖\r\n```\r\n\r\n## 测试右移\r\n\r\n### 右移策略\r\n\r\n```\r\n发布阶段：\r\n├─ 灰度发布：按比例放量\r\n├─ 监控告警：实时监控\r\n├─ 快速回滚：问题时快速回滚\r\n└─ 线上验证：验证发布效果\r\n\r\n线上阶段：\r\n├─ 业务监控：业务指标监控\r\n├─ 技术监控：技术指标监控\r\n├─ 用户反馈：用户问题收集\r\n└─ 混沌工程：主动注入故障\r\n```\r\n\r\n### 右移实践\r\n\r\n```\r\n实践1：灰度发布\r\n├─ 用户灰度：按用户比例\r\n├─ 流量灰度：按流量比例\r\n├─ 地域灰度：按地域\r\n└─ 监控验证：实时监控\r\n\r\n实践2：线上监控\r\n├─ 业务监控：订单量、成功率\r\n├─ 技术监控：错误率、响应时间\r\n├─ 资源监控：CPU、内存、磁盘\r\n└─ 告警通知：异常告警\r\n\r\n实践3：混沌工程\r\n├─ 故障注入：模拟故障\r\n├─ 韧性验证：验证系统韧性\r\n├─ 恢复测试：验证恢复能力\r\n└─ 改进优化：持续改进\r\n```\r\n\r\n## CI/CD 流水线设计\r\n\r\n### 流水线阶段\r\n\r\n```\r\n代码提交 → 代码检查 → 单元测试 → 接口测试 → 集成测试 → 部署 → 冒烟测试 → 灰度发布 → 全量发布\r\n\r\n各阶段职责：\r\n├─ 代码提交：提交代码\r\n├─ 代码检查：静态代码分析\r\n├─ 单元测试：执行单元测试\r\n├─ 接口测试：执行接口测试\r\n├─ 集成测试：执行集成测试\r\n├─ 部署：部署到测试环境\r\n├─ 冒烟测试：执行冒烟测试\r\n├─ 灰度发布：按比例发布\r\n└─ 全量发布：全量发布\r\n```\r\n\r\n### 质量门禁\r\n\r\n```\r\n门禁标准：\r\n├─ 代码检查\r\n│   ├─ 代码规范：无严重违规\r\n│   ├─ 代码重复：< 5%\r\n│   └─ 圈复杂度：< 10\r\n│\r\n├─ 单元测试\r\n│   ├─ 覆盖率：≥ 80%\r\n│   ├─ 通过率：100%\r\n│   └─ 执行时间：< 5分钟\r\n│\r\n├─ 接口测试\r\n│   ├─ 覆盖率：≥ 90%\r\n│   ├─ 通过率：100%\r\n│   └─ 执行时间：< 10分钟\r\n│\r\n├─ 集成测试\r\n│   ├─ 通过率：100%\r\n│   └─ 执行时间：< 30分钟\r\n│\r\n└─ 冒烟测试\r\n    ├─ 通过率：100%\r\n    └─ 核心功能：全部通过\r\n```\r\n\r\n### 工具选型\r\n\r\n```\r\n├─ 代码管理\r\n│   ├─ Git：版本控制\r\n│   └─ GitLab/GitHub：代码托管\r\n│\r\n├─ CI/CD工具\r\n│   ├─ Jenkins：开源、灵活\r\n│   ├─ GitLab CI：集成度高\r\n│   ├─ GitHub Actions：云端友好\r\n│   └─ CircleCI：云端CI\r\n│\r\n├─ 测试工具\r\n│   ├─ JUnit/TestNG：单元测试\r\n│   ├─ Pytest：Python测试\r\n│   ├─ Postman/Newman：接口测试\r\n│   └─ Selenium/Playwright：UI测试\r\n│\r\n└─ 报告工具\r\n    ├─ Allure：测试报告\r\n    ├─ SonarQube：代码质量\r\n    └─ Grafana：监控可视化\r\n```\r\n\r\n## Examples\r\n\r\n**团队需要将测试接入CI/CD流水线**\r\n→ 设计流水线阶段：提交触发→单元测试→接口测试→UI测试→质量门禁→报告\r\n→ 左移：需求阶段定义验收标准，开发阶段推动单元测试\r\n→ 右移：灰度发布监控指标，线上质量监控告警\r\n\r\n**现有CI/CD测试效率低下（跑一次1小时）**\r\n→ 优化策略：分层并行执行、增量测试、智能用例筛选\r\n\r\n## Guidelines\r\n\r\n持续测试实践完成后检查：\r\n- [ ] 测试左移是否实施？\r\n- [ ] 测试右移是否规划？\r\n- [ ] CI/CD流水线是否设计？\r\n- [ ] 质量门禁是否定义？\r\n- [ ] 工具选型是否完成？\r\n- [ ] 监控告警是否配置？\n\nFile v1.4.0:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-ci-cd-testing\",\n  \"version\": \"1.4.0\",\n  \"publishedAt\": 1782277562968\n}\n\nFile v1.4.0:skill-card.md\n\n## Description: <br>\nProvides Chinese-language guidance for integrating continuous testing into CI/CD pipelines, including pipeline design, quality gates, tool integration, and monitoring practices. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[kokxi](https://clawhub.ai/user/kokxi) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers, QA engineers, and release engineers use this skill to design or improve CI/CD testing workflows, automated quality gates, shift-left and shift-right testing practices, and pipeline efficiency. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Broad CI/CD and pipeline activation wording may cause the skill to trigger on general pipeline discussions. <br>\nMitigation: Confirm the user wants CI/CD testing workflow guidance before applying recommendations. <br>\nRisk: The skill declares Bash access, which may exceed what stricter environments allow for a guidance-focused workflow. <br>\nMitigation: Review or restrict Bash permissions before installation in environments with tighter tool access policies. <br>\nRisk: CI/CD quality gate or release workflow advice can affect build, test, and deployment decisions. <br>\nMitigation: Have engineers review proposed pipeline changes and test them outside production before rollout. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/kokxi/skills/qa-ci-cd-testing) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Guidance, Markdown, Configuration] <br>\n**Output Format:** [Markdown text] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Chinese-language CI/CD testing recommendations and checklists.] <br>\n\n## Skill Version(s): <br>\n1.4.0 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.3.0: 3 files, 3419 bytes\n\nFiles: skill-card.md (1890b), SKILL.md (5165b), _meta.json (135b)\n\nFile v1.3.0:SKILL.md\n\n---\r\nname: qa-ci-cd-testing\r\ndescription: 持续测试实践，将测试集成到CI/CD流程中。当需要设计或优化CI/CD测试流程时激活。\r\nwhen_to_use: 用户说\"CI/CD\"、\"持续测试\"、\"自动化测试\"、需要设计CI/CD测试流程时\r\nallowed-tools: Read Grep Glob Bash\r\nrelated_skills:\r\n  upstream:\r\n    - qa-tech-selection          # 输入：技术选型确定工具栈\r\n    - qa-test-strategy-design    # 输入：测试策略确定自动化范围\r\n  downstream:\r\n    - qa-release-risk-governance # 输出：CI/CD流程支持发布\r\ninput_format: 技术选型 + 测试策略\r\noutput_format: CI/CD测试方案（流水线设计+质量门禁+工具集成）\r\n---\r\n\r\n# 持续测试实践\r\n\r\n你是一位持续测试专家，擅长将测试集成到CI/CD流程中。\r\n\r\n## 核心原则\r\n\r\n**测试左移（提前测试）、测试右移（线上验证）、快速反馈。**\r\n\r\n## 测试左移\r\n\r\n### 左移策略\r\n\r\n```\r\n需求阶段：\r\n├─ 需求评审：测试参与需求评审\r\n├─ 验收标准：明确验收条件\r\n├─ 可测试性：评估可测试性\r\n└─ 测试计划：制定测试计划\r\n\r\n开发阶段：\r\n├─ 代码评审：测试视角的CR\r\n├─ 单元测试：开发编写单元测试\r\n├─ 接口测试：测试编写接口测试\r\n└─ 冒烟测试：开发自测通过\r\n\r\n集成阶段：\r\n├─ 接口自动化：自动执行接口测试\r\n├─ 集成测试：自动执行集成测试\r\n└─ 冒烟测试：自动执行冒烟测试\r\n```\r\n\r\n### 左移实践\r\n\r\n```\r\n实践1：需求可测试性评估\r\n├─ 验收条件是否明确？\r\n├─ 是否可自动化验证？\r\n├─ 测试数据是否可准备？\r\n└─ 测试环境是否可搭建？\r\n\r\n实践2：代码评审检查点\r\n├─ 业务逻辑是否正确？\r\n├─ 异常处理是否完善？\r\n├─ 日志记录是否完整？\r\n└─ 测试代码是否同步？\r\n\r\n实践3：单元测试覆盖\r\n├─ 核心逻辑单元测试\r\n├─ 分支覆盖\r\n├─ 边界覆盖\r\n└─ 异常覆盖\r\n```\r\n\r\n## 测试右移\r\n\r\n### 右移策略\r\n\r\n```\r\n发布阶段：\r\n├─ 灰度发布：按比例放量\r\n├─ 监控告警：实时监控\r\n├─ 快速回滚：问题时快速回滚\r\n└─ 线上验证：验证发布效果\r\n\r\n线上阶段：\r\n├─ 业务监控：业务指标监控\r\n├─ 技术监控：技术指标监控\r\n├─ 用户反馈：用户问题收集\r\n└─ 混沌工程：主动注入故障\r\n```\r\n\r\n### 右移实践\r\n\r\n```\r\n实践1：灰度发布\r\n├─ 用户灰度：按用户比例\r\n├─ 流量灰度：按流量比例\r\n├─ 地域灰度：按地域\r\n└─ 监控验证：实时监控\r\n\r\n实践2：线上监控\r\n├─ 业务监控：订单量、成功率\r\n├─ 技术监控：错误率、响应时间\r\n├─ 资源监控：CPU、内存、磁盘\r\n└─ 告警通知：异常告警\r\n\r\n实践3：混沌工程\r\n├─ 故障注入：模拟故障\r\n├─ 韧性验证：验证系统韧性\r\n├─ 恢复测试：验证恢复能力\r\n└─ 改进优化：持续改进\r\n```\r\n\r\n## CI/CD 流水线设计\r\n\r\n### 流水线阶段\r\n\r\n```\r\n代码提交 → 代码检查 → 单元测试 → 接口测试 → 集成测试 → 部署 → 冒烟测试 → 灰度发布 → 全量发布\r\n\r\n各阶段职责：\r\n├─ 代码提交：提交代码\r\n├─ 代码检查：静态代码分析\r\n├─ 单元测试：执行单元测试\r\n├─ 接口测试：执行接口测试\r\n├─ 集成测试：执行集成测试\r\n├─ 部署：部署到测试环境\r\n├─ 冒烟测试：执行冒烟测试\r\n├─ 灰度发布：按比例发布\r\n└─ 全量发布：全量发布\r\n```\r\n\r\n### 质量门禁\r\n\r\n```\r\n门禁标准：\r\n├─ 代码检查\r\n│   ├─ 代码规范：无严重违规\r\n│   ├─ 代码重复：< 5%\r\n│   └─ 圈复杂度：< 10\r\n│\r\n├─ 单元测试\r\n│   ├─ 覆盖率：≥ 80%\r\n│   ├─ 通过率：100%\r\n│   └─ 执行时间：< 5分钟\r\n│\r\n├─ 接口测试\r\n│   ├─ 覆盖率：≥ 90%\r\n│   ├─ 通过率：100%\r\n│   └─ 执行时间：< 10分钟\r\n│\r\n├─ 集成测试\r\n│   ├─ 通过率：100%\r\n│   └─ 执行时间：< 30分钟\r\n│\r\n└─ 冒烟测试\r\n    ├─ 通过率：100%\r\n    └─ 核心功能：全部通过\r\n```\r\n\r\n### 工具选型\r\n\r\n```\r\n├─ 代码管理\r\n│   ├─ Git：版本控制\r\n│   └─ GitLab/GitHub：代码托管\r\n│\r\n├─ CI/CD工具\r\n│   ├─ Jenkins：开源、灵活\r\n│   ├─ GitLab CI：集成度高\r\n│   ├─ GitHub Actions：云端友好\r\n│   └─ CircleCI：云端CI\r\n│\r\n├─ 测试工具\r\n│   ├─ JUnit/TestNG：单元测试\r\n│   ├─ Pytest：Python测试\r\n│   ├─ Postman/Newman：接口测试\r\n│   └─ Selenium/Playwright：UI测试\r\n│\r\n└─ 报告工具\r\n    ├─ Allure：测试报告\r\n    ├─ SonarQube：代码质量\r\n    └─ Grafana：监控可视化\r\n```\r\n\r\n## 验收清单\r\n\r\n持续测试实践完成后检查：\r\n- [ ] 测试左移是否实施？\r\n- [ ] 测试右移是否规划？\r\n- [ ] CI/CD流水线是否设计？\r\n- [ ] 质量门禁是否定义？\r\n- [ ] 工具选型是否完成？\r\n- [ ] 监控告警是否配置？\n\nFile v1.3.0:_meta.json\n\n{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-ci-cd-testing\",\n  \"version\": \"1.3.0\",\n  \"publishedAt\": 1782056267435\n}\n\nFile v1.3.0:skill-card.md\n\n## Description: <br>\nGuides agents in designing or optimizing CI/CD testing workflows with continuous testing practices, pipeline stages, quality gates, and tool choices. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[kokxi](https://clawhub.ai/user/kokxi) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nQA engineers, developers, and release engineers use this skill to plan CI/CD testing workflows, define quality gates, and integrate automated testing practices into delivery pipelines. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may activate on broad CI/CD or automated-testing mentions. <br>\nMitigation: Narrow the trigger wording or invoke it only when explicitly designing or optimizing a CI/CD testing pipeline. <br>\nRisk: Pipeline and quality-gate recommendations may need adjustment for a team's stack, risk tolerance, and release process. <br>\nMitigation: Review proposed gates, thresholds, and tool choices before applying them to production delivery workflows. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/kokxi/qa-ci-cd-testing) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Guidance, Markdown, Configuration instructions] <br>\n**Output Format:** [Markdown or structured text] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces CI/CD testing plans, quality-gate criteria, tool-selection guidance, and implementation checklists.] <br>\n\n## Skill Version(s): <br>\n1.3.0 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>","readmeExcerpt":"Skill: qa-ci-cd-testing Owner: kokxi Summary: 当需要把测试集成到 CI/CD 流水线中、或者现有流水线的测试环节跑起来效率低不可靠时使用此技能。覆盖流水线各阶段的分层测试卡点设计（提交检查→单元测试→接口测试→UI 测试→回归测试）、工具集成策略和质量门禁配置。不要在 CI 里堆满慢的 UI 测试——而是构建测试金字塔：提交阶段跑最快的（<5min），合码阶段跑核心的（<15min），夜间跑全量的。 触发场景：CI/CD、持续测试、流水线测试、质量门禁、自动化回归、提交即测试、构建流水线需要加入测试环节时。 Use when the user asks about: integrating tests into a CI/CD pipeline — layered quality gates, fast commit-stage tests, and release blocking","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"需求阶段：\n├─ 需求评审：测试参与需求评审\n├─ 验收标准：明确验收条件\n├─ 可测试性：评估可测试性\n└─ 测试计划：制定测试计划\n\n开发阶段：\n├─ 代码评审：测试视角的CR\n├─ 单元测试：开发编写单元测试\n├─ 接口测试：测试编写接口测试\n└─ 冒烟测试：开发自测通过\n\n集成阶段：\n├─ 接口自动化：自动执行接口测试\n├─ 集成测试：自动执行集成测试\n└─ 冒烟测试：自动执行冒烟测试"},{"language":"text","snippet":"实践1：需求可测试性评估\n├─ 验收条件是否明确？\n├─ 是否可自动化验证？\n├─ 测试数据是否可准备？\n└─ 测试环境是否可搭建？\n\n实践2：代码评审检查点\n├─ 业务逻辑是否正确？\n├─ 异常处理是否完善？\n├─ 日志记录是否完整？\n└─ 测试代码是否同步？\n\n实践3：单元测试覆盖\n├─ 核心逻辑单元测试\n├─ 分支覆盖\n├─ 边界覆盖\n└─ 异常覆盖"},{"language":"text","snippet":"发布阶段：\n├─ 灰度发布：按比例放量\n├─ 监控告警：实时监控\n├─ 快速回滚：问题时快速回滚\n└─ 线上验证：验证发布效果\n\n线上阶段：\n├─ 业务监控：业务指标监控\n├─ 技术监控：技术指标监控\n├─ 用户反馈：用户问题收集\n└─ 混沌工程：主动注入故障"},{"language":"text","snippet":"实践1：灰度发布\n├─ 用户灰度：按用户比例\n├─ 流量灰度：按流量比例\n├─ 地域灰度：按地域\n└─ 监控验证：实时监控\n\n实践2：线上监控\n├─ 业务监控：订单量、成功率\n├─ 技术监控：错误率、响应时间\n├─ 资源监控：CPU、内存、磁盘\n└─ 告警通知：异常告警\n\n实践3：混沌工程\n├─ 故障注入：模拟故障\n├─ 韧性验证：验证系统韧性\n├─ 恢复测试：验证恢复能力\n└─ 改进优化：持续改进"},{"language":"text","snippet":"代码提交 → 代码检查 → 单元测试 → 接口测试 → 集成测试 → 部署 → 冒烟测试 → 灰度发布 → 全量发布\n\n各阶段职责：\n├─ 代码提交：提交代码\n├─ 代码检查：静态代码分析\n├─ 单元测试：执行单元测试\n├─ 接口测试：执行接口测试\n├─ 集成测试：执行集成测试\n├─ 部署：部署到测试环境\n├─ 冒烟测试：执行冒烟测试\n├─ 灰度发布：按比例发布\n└─ 全量发布：全量发布"},{"language":"text","snippet":"门禁标准：\n├─ 代码检查\n│   ├─ 代码规范：无严重违规\n│   ├─ 代码重复：< 5%\n│   └─ 圈复杂度：< 10\n│\n├─ 单元测试\n│   ├─ 覆盖率：≥ 80%\n│   ├─ 通过率：100%\n│   └─ 执行时间：< 5分钟\n│\n├─ 接口测试\n│   ├─ 覆盖率：≥ 90%\n│   ├─ 通过率：100%\n│   └─ 执行时间：< 10分钟\n│\n├─ 集成测试\n│   ├─ 通过率：100%\n│   └─ 执行时间：< 30分钟\n│\n└─ 冒烟测试\n    ├─ 通过率：100%\n    └─ 核心功能：全部通过"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: qa-ci-cd-testing\ndescription: >-\n  当需要把测试集成到 CI/CD 流水线中、或者现有流水线的测试环节跑起来效率低不可靠时使用此技能。覆盖流水线各阶段的分层测试卡点设计（提交检查→单元测试→接口测试→UI 测试→回归测试）、工具集成策略和质量门禁配置。不要在 CI 里堆满慢的 UI 测试——而是构建测试金字塔：提交阶段跑最快的（<5min），合码阶段跑核心的（<15min），夜间跑全量的。 触发场景：CI/CD、持续测试、流水线测试、质量门禁、自动化回归、提交即测试、构建流水线需要加入测试环节时。 Use when the user asks about: integrating tests into a CI/CD pipeline — layered quality gates, fast commit-stage tests, and release blocking criteria.\nlicense: MIT\nallowed-tools: Read Grep Glob Bash\nmetadata:\n  display-name: \"Ci Cd Testing\"\n  version: \"1.8.0\"\n  when-to-use: \"用户说\\\"CI/CD\\\"、\\\"持续测试\\\"、\\\"流水线测试\\\"、\\\"质量门禁\\\"、\\\"自动化回归\\\"、\\\"提交即测试\\\"、需要设计CI/CD测试流程、构建流水线需要加入测试环节时\"\n  related-skills: \"{\\\"upstream\\\":[\\\"qa-tech-selection\\\",\\\"qa-test-strategy-design\\\"],\\\"downstream\\\":[\\\"qa-release-risk-governance\\\",\\\"qa-shift-right\\\"]}\"\n  references: \"[\\\"references/pipeline-design.md\\\"]\"\n  input-format: \"{\\\"required\\\":[{\\\"name\\\":\\\"测试策略\\\",\\\"type\\\":\\\"object\\\",\\\"description\\\":\\\"来自qa-test-strategy-design的测试策略\\\"},{\\\"name\\\":\\\"自动化架构\\\",\\\"type\\\":\\\"object\\\",\\\"description\\\":\\\"来自qa-test-automation-arch的自动化架构\\\"}],\\\"optional\\\":[{\\\"name\\\":\\\"流水线配置\\\",\\\"type\\\":\\\"string\\\",\\\"description\\\":\\\"CI/CD流水线配置信息\\\"}]}\"\n  output-format: \"{\\\"traceability\\\":[\\\"每条流水线带唯一ID（PIPE-XXXX）\\\"],\\\"structure\\\":[\\\"覆盖率：标注口径（基于现有需求/输入文档），禁止\\\\\\\"全覆盖/100%\\\\\\\"绝对化表述；缺失模块标注\\\\\\\"未覆盖+原因\\\\\\\"\\\",{\\\"pipeline_design\\\":\\\"CI/CD流水线设计\\\"},{\\\"test_stages\\\":\\\"各阶段测试配置\\\"},{\\\"quality_gates\\\":\\\"质量门禁设置\\\"},{\\\"feedback_loops\\\":\\\"反馈循环机制\\\"}]}\"\n  error-recovery-guidance: \"{\\\"on_failure\\\":\\\"流水线测试卡点失败时回退到测试策略调整范围\\\",\\\"retry_behavior\\\":\\\"调整测试范围或工具后重新配置卡点\\\"}\"\n  categories: \"[\\\"Development\\\",\\\"Testing\\\",\\\"DevOps\\\"]\"\n  depth-requirement: \"{\\\"reference_value\\\":\\\"根据流水线复杂度调整设计深度：简单×1/中等×2/复杂×3\\\",\\\"minimum\\\":\\\"至少覆盖提交检查、接口测试、回归测试3个卡点\\\"}\"\n---\n> ⚠️ 本技能单独使用效果有限，建议配合完整技能集（12 步工作流）使用。安装：npx skills add Kokxi/qa-test-skills\n\n> **⚠️ 安全警告**：本技能的示例可能涉及 CI/CD 流水线配置、发布操作和部署环境。\n> 实际使用时请勿在未授权的生产环境执行发布或部署，先确认灰度策略和回滚方案。\n> 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。\n\n# 持续测试实践\n\n## 核心原则\n\n测试左移（提前测试）、测试右移（线上验证）、快速反馈。\n\n## 深度要求（参考值）\n\n**关键指标**：根据项目复杂度设计质量门禁策略\n\n| 复杂度 | 流水线阶段 | 质量门禁阈值 | 说明 |\n|--------|-----------|-------------|------|\n| 简单项目 | 2-3个阶段 | 单元测试通过率≥80% | 标准CI流程 |\n| 中等项目 | 4-5个阶段 | 单元≥90%+接口通过率≥95% | 含集成测试 |\n| 复杂项目 | 6-8个阶段 | 全链路≥95%+性能阈值 | 含全量自动化+安全扫描 |\n\n## 测试左移\n\n### 左移策略\n\n```text\n需求阶段：\n├─ 需求评审：测试参与需求评审\n├─ 验收标准：明确验收条件\n├─ 可测试性：评估可测试性\n└─ 测试计划：制定测试计划\n\n开发阶段：\n├─ 代码评审：测试视角的CR\n├─ 单元测试：开发编写单元测试\n├─ 接口测试：测试编写接口测试\n└─ 冒烟测试：开发自测通过\n\n集成阶段：\n├─ 接口自动化：自动执行接口测试\n├─ 集成测试：自动执行集成测试\n└─ 冒烟测试：自动执行冒烟测试\n```\n\n### 左移实践\n\n```text\n实践1：需求可测试性评估\n├─ 验收条件是否明确？\n├─ 是否可自动化验证？\n├─ 测试数据是否可准备？\n└─ 测试环境是否可搭建？\n\n实践2：代码评审检查点\n├─ 业务逻辑是否正确？\n├─ 异常处理是否完善？\n├─ 日志记录是否完整？\n└─ 测试代码是否同步？\n\n实践3：单元测试覆盖\n├─ 核心逻辑单元测试\n├─ 分支覆盖\n├─ 边界覆盖\n└─ 异常覆盖\n```\n\n## 测试右移\n\n### 右移策略\n\n```text\n发布阶段：\n├─ 灰度发布：按比例放量\n├─ 监控告警：实时监控\n├─ 快速回滚：问题时快速回滚\n└─ 线上验证：验证发布效果\n\n线上阶段：\n├─ 业务监控：业务指标监控\n├─ 技术监控：技术指标监控\n├─ 用户反馈：用户问题收集\n└─ 混沌工程：主动注入故障\n```\n\n### 右移实践\n\n```text\n实践1：灰度发布\n├─ 用户灰度：按用户比例\n├─ 流量灰度：按流量比例\n├─ 地域灰度：按地域\n└─ 监控验证：实时监控\n\n实践2：线上监控\n├─ 业务监控：订单量、成功率\n├─ 技术监控：错误率、响应时间\n├─ 资源监控：CPU、内存、磁盘\n└─ 告警通知：异常告警\n\n实践3：混沌工程"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn71y9b23csfx0ykgm55d5m9x5891zt8\",\n  \"slug\": \"qa-ci-cd-testing\",\n  \"version\": \"1.8.0\",\n  \"publishedAt\": 1790655955679\n}"},{"path":"references/pipeline-design.md","content":"# CI/CD 流水线设计详解\n\n> 本文是 `qa-ci-cd-testing` 的**CI/CD 流水线设计详解**。设计流水线分层卡点时读本文；\n其余部分留在 SKILL.md，不必读本文。\n\n---\n\n\n### 流水线阶段\n\n```text\n代码提交 → 代码检查 → 单元测试 → 接口测试 → 集成测试 → 部署 → 冒烟测试 → 灰度发布 → 全量发布\n\n各阶段职责：\n├─ 代码提交：提交代码\n├─ 代码检查：静态代码分析\n├─ 单元测试：执行单元测试\n├─ 接口测试：执行接口测试\n├─ 集成测试：执行集成测试\n├─ 部署：部署到测试环境\n├─ 冒烟测试：执行冒烟测试\n├─ 灰度发布：按比例发布\n└─ 全量发布：全量发布\n```\n\n### 质量门禁\n\n```text\n门禁标准：\n├─ 代码检查\n│   ├─ 代码规范：无严重违规\n│   ├─ 代码重复：< 5%\n│   └─ 圈复杂度：< 10\n│\n├─ 单元测试\n│   ├─ 覆盖率：≥ 80%\n│   ├─ 通过率：100%\n│   └─ 执行时间：< 5分钟\n│\n├─ 接口测试\n│   ├─ 覆盖率：≥ 90%\n│   ├─ 通过率：100%\n│   └─ 执行时间：< 10分钟\n│\n├─ 集成测试\n│   ├─ 通过率：100%\n│   └─ 执行时间：< 30分钟\n│\n└─ 冒烟测试\n    ├─ 通过率：100%\n    └─ 核心功能：全部通过\n```\n\n### 工具选型\n\n```text\n├─ 代码管理\n│   ├─ Git：版本控制\n│   └─ GitLab/GitHub：代码托管\n│\n├─ CI/CD工具\n│   ├─ Jenkins：开源、灵活\n│   ├─ GitLab CI：集成度高\n│   ├─ GitHub Actions：云端友好\n│   └─ CircleCI：云端CI\n│\n├─ 测试工具\n│   ├─ JUnit/TestNG：单元测试\n│   ├─ Pytest：Python测试\n│   ├─ Postman/Newman：接口测试\n│   └─ Selenium/Playwright：UI测试\n│\n└─ 报告工具\n    ├─ Allure：测试报告\n    ├─ SonarQube：代码质量\n    └─ Grafana：监控可视化\n```"},{"path":"skill-card.md","content":"## Description:\n\nHelps teams design staged CI/CD testing, quality gates, and feedback loops for faster, more reliable releases.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kokxi](https://clawhub.ai/user/kokxi)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and QA engineers use this skill to plan layered tests, quality gates, and release feedback across CI/CD stages, including fast commit checks and regression testing.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The optional installation command fetches an unpinned skill package.\n\nMitigation: Review the command and package before using it.\n\nRisk: Applying deployment or release recommendations without safeguards could affect production systems.\n\nMitigation: Use only in authorized environments with a reviewed rollout and rollback plan.\n\n## Reference(s):\n\n- [CI/CD pipeline design reference](references/pipeline-design.md)\n- [ClawHub skill release](https://clawhub.ai/kokxi/skills/qa-ci-cd-testing)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Configuration instructions, Markdown]\n\n**Output Format:** [Markdown pipeline design with test stages, quality gates, and feedback loops]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Pipeline IDs use PIPE-XXXX; coverage statements identify their basis and explain uncovered modules.]\n\n## Skill Version(s):\n\n1.8.0 (source: skill frontmatter and server release)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"当需要把测试集成到 CI/CD 流水线中、或者现有流水线的测试环节跑起来效率低不可靠时使用此技能。覆盖流水线各阶段的分层测试卡点设计（提交检查→单元测试→接口测试→UI 测试→回归测试）、工具集成策略和质量门禁配置。不要在 CI 里堆满慢的 UI 测试——而是构建测试金字塔：提交阶段跑最快的（<5min），合码阶段跑核心的（<15min），夜间跑全量的。 触发场景：CI/CD、持续测试、流水线测试、质量门禁、自动化回归、提交即测试、构建流水线需要加入测试环节时。 Use when the user asks about: integrating tests into a CI/CD pipeline — layered quality gates, fast commit-stage tests, and release blocking criteria. Skill: qa-ci-cd-testing Owner: kokxi Summary: 当需要把测试集成到 CI/CD 流水线中、或者现有流水线的测试环节跑起来效率低不可靠时使用此技能。覆盖流水线各阶段的分层测试卡点设计（提交检查→单元测试→接口测试→UI 测试→回归测试）、工具集成策略和质量门禁配置。不要在 CI 里堆满慢的 UI 测试——而是构建测试金字塔：提交阶段跑最快的（<5min），合码阶段跑核心的（<15min），夜间跑全量的。 触发场景：CI/CD、持续测试、流水线测试、质量门禁、自动化回归、提交即测试、构建流水线需要加入测试环节时。 Use when the user asks about: integrating tests into a CI/CD pipeline — layered quality gates, fast commit-stage tests, and release blocking","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":999,"uniquenessScore":51,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T01:53:53.316Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T01:53:53.316Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T04:34:00.143Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}