[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DS5F8DF79KRK721N7MBHSK":3,"skill-same:01M6DS5F8DF79KRK721N7MBHSK":85},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M6DS5F8DF79KRK721N7MBHSK","ci-cd-pipeline-builder",null,"CI\u002FCD Pipeline Builder","zhangzhang-111-i\u002Fclaude-skills111","zhangzhang-111-i","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F251344927?v=4","01M6DRBP4NCM1ZCHTT0FW0SQHD","lixiying","01M6DRBPAMFDJSGQ69XPK9KM9J",4,"MIT","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fci-cd-pipeline-builder\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[24,25,26,27,28,29,30],"ci cd","ci","pipeline","ci cd pipeline builder","builder","ci cd pipeline","cd","2026-11-10 10:12:30",false,"---\nname: \"ci-cd-pipeline-builder\"\ndescription: \"CI\u002FCD Pipeline Builder\"\n---\n\n# CI\u002FCD Pipeline Builder\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Domain:** DevOps \u002F Automation\n\n## Overview\n\nUse this skill to generate pragmatic CI\u002FCD pipelines from detected project stack signals, not guesswork. It focuses on fast baseline generation, repeatable checks, and environment-aware deployment stages.\n\n## Core Capabilities\n\n- Detect language\u002Fruntime\u002Ftooling from repository files\n- Recommend CI stages (`lint`, `test`, `build`, `deploy`)\n- Generate GitHub Actions or GitLab CI starter pipelines\n- Include caching and matrix strategy based on detected stack\n- Emit machine-readable detection output for automation\n- Keep pipeline logic aligned with project lockfiles and build commands\n\n## When to Use\n\n- Bootstrapping CI for a new repository\n- Replacing brittle copied pipeline files\n- Migrating between GitHub Actions and GitLab CI\n- Auditing whether pipeline steps match actual stack\n- Creating a reproducible baseline before custom hardening\n\n## Key Workflows\n\n### 1. Detect Stack\n\n```bash\npython3 scripts\u002Fstack_detector.py --repo . --format text\npython3 scripts\u002Fstack_detector.py --repo . --format json > detected-stack.json\n```\n\nSupports input via stdin or `--input` file for offline analysis payloads.\n\n### 2. Generate Pipeline From Detection\n\n```bash\npython3 scripts\u002Fpipeline_generator.py \\\n  --input detected-stack.json \\\n  --platform github \\\n  --output .github\u002Fworkflows\u002Fci.yml \\\n  --format text\n```\n\nOr end-to-end from repo directly:\n\n```bash\npython3 scripts\u002Fpipeline_generator.py --repo . --platform gitlab --output .gitlab-ci.yml\n```\n\n### 3. Validate Before Merge\n\n1. Confirm commands exist in project (`test`, `lint`, `build`).\n2. Run generated pipeline locally where possible.\n3. Ensure required secrets\u002Fenv vars are documented.\n4. Keep deploy jobs gated by protected branches\u002Fenvironments.\n\n### 4. Add Deployment Stages Safely\n\n- Start with CI-only (`lint\u002Ftest\u002Fbuild`).\n- Add staging deploy with explicit environment context.\n- Add production deploy with manual gate\u002Fapproval.\n- Keep rollout\u002Frollback commands explicit and auditable.\n\n## Script Interfaces\n\n- `python3 scripts\u002Fstack_detector.py --help`\n  - Detects stack signals from repository files\n  - Reads optional JSON input from stdin\u002F`--input`\n- `python3 scripts\u002Fpipeline_generator.py --help`\n  - Generates GitHub\u002FGitLab YAML from detection payload\n  - Writes to stdout or `--output`\n\n## Common Pitfalls\n\n1. Copying a Node pipeline into Python\u002FGo repos\n2. Enabling deploy jobs before stable tests\n3. Forgetting dependency cache keys\n4. Running expensive matrix builds for every trivial branch\n5. Missing branch protections around prod deploy jobs\n6. Hardcoding secrets in YAML instead of CI secret stores\n\n## Best Practices\n\n1. Detect stack first, then generate pipeline.\n2. Keep generated baseline under version control.\n3. Add one optimization at a time (cache, matrix, split jobs).\n4. Require green CI before deployment jobs.\n5. Use protected environments for production credentials.\n6. Regenerate pipeline when stack changes significantly.\n\n## References\n\n- [references\u002Fgithub-actions-templates.md](references\u002Fgithub-actions-templates.md)\n- [references\u002Fgitlab-ci-templates.md](references\u002Fgitlab-ci-templates.md)\n- [references\u002Fdeployment-gates.md](references\u002Fdeployment-gates.md)\n- [README.md](README.md)\n\n## Detection Heuristics\n\nThe stack detector prioritizes deterministic file signals over heuristics:\n\n- Lockfiles determine package manager preference\n- Language manifests determine runtime families\n- Script commands (if present) drive lint\u002Ftest\u002Fbuild commands\n- Missing scripts trigger conservative placeholder commands\n\n## Generation Strategy\n\nStart with a minimal, reliable pipeline:\n\n1. Checkout and setup runtime\n2. Install dependencies with cache strategy\n3. Run lint, test, build in separate steps\n4. Publish artifacts only after passing checks\n\nThen layer advanced behavior (matrix builds, security scans, deploy gates).\n\n## Platform Decision Notes\n\n- GitHub Actions for tight GitHub ecosystem integration\n- GitLab CI for integrated SCM + CI in self-hosted environments\n- Keep one canonical pipeline source per repo to reduce drift\n\n## Validation Checklist\n\n1. Generated YAML parses successfully.\n2. All referenced commands exist in the repo.\n3. Cache strategy matches package manager.\n4. Required secrets are documented, not embedded.\n5. Branch\u002Fprotected-environment rules match org policy.\n\n## Scaling Guidance\n\n- Split long jobs by stage when runtime exceeds 10 minutes.\n- Introduce test matrix only when compatibility truly requires it.\n- Separate deploy jobs from CI jobs to keep feedback fast.\n- Track pipeline duration and flakiness as first-class metrics.\n","# CI\u002FCD Pipeline Builder\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Domain:** DevOps \u002F Automation\n\n## Overview\n\nUse this skill to generate pragmatic CI\u002FCD pipelines from detected project stack signals, not guesswork. It focuses on fast baseline generation, repeatable checks, and environment-aware deployment stages.\n\n## Core Capabilities\n\n- Detect language\u002Fruntime\u002Ftooling from repository files\n- Recommend CI stages (`lint`, `test`, `build`, `deploy`)\n- Generate GitHub Actions or GitLab CI starter pipelines\n- Include caching and matrix strategy based on detected stack\n- Emit machine-readable detection output for automation\n- Keep pipeline logic aligned with project lockfiles and build commands\n\n## When to Use\n\n- Bootstrapping CI for a new repository\n- Replacing brittle copied pipeline files\n- Migrating between GitHub Actions and GitLab CI\n- Auditing whether pipeline steps match actual stack\n- Creating a reproducible baseline before custom hardening\n\n## Key Workflows\n\n### 1. Detect Stack\n\n```bash\npython3 scripts\u002Fstack_detector.py --repo . --format text\npython3 scripts\u002Fstack_detector.py --repo . --format json > detected-stack.json\n```\n\nSupports input via stdin or `--input` file for offline analysis payloads.\n\n### 2. Generate Pipeline From Detection\n\n```bash\npython3 scripts\u002Fpipeline_generator.py \\\n  --input detected-stack.json \\\n  --platform github \\\n  --output .github\u002Fworkflows\u002Fci.yml \\\n  --format text\n```\n\nOr end-to-end from repo directly:\n\n```bash\npython3 scripts\u002Fpipeline_generator.py --repo . --platform gitlab --output .gitlab-ci.yml\n```\n\n### 3. Validate Before Merge\n\n1. Confirm commands exist in project (`test`, `lint`, `build`).\n2. Run generated pipeline locally where possible.\n3. Ensure required secrets\u002Fenv vars are documented.\n4. Keep deploy jobs gated by protected branches\u002Fenvironments.\n\n### 4. Add Deployment Stages Safely\n\n- Start with CI-only (`lint\u002Ftest\u002Fbuild`).\n- Add staging deploy with explicit environment context.\n- Add production deploy with manual gate\u002Fapproval.\n- Keep rollout\u002Frollback commands explicit and auditable.\n\n## Script Interfaces\n\n- `python3 scripts\u002Fstack_detector.py --help`\n  - Detects stack signals from repository files\n  - Reads optional JSON input from stdin\u002F`--input`\n- `python3 scripts\u002Fpipeline_generator.py --help`\n  - Generates GitHub\u002FGitLab YAML from detection payload\n  - Writes to stdout or `--output`\n\n## Common Pitfalls\n\n1. Copying a Node pipeline into Python\u002FGo repos\n2. Enabling deploy jobs before stable tests\n3. Forgetting dependency cache keys\n4. Running expensive matrix builds for every trivial branch\n5. Missing branch protections around prod deploy jobs\n6. Hardcoding secrets in YAML instead of CI secret stores\n\n## Best Practices\n\n1. Detect stack first, then generate pipeline.\n2. Keep generated baseline under version control.\n3. Add one optimization at a time (cache, matrix, split jobs).\n4. Require green CI before deployment jobs.\n5. Use protected environments for production credentials.\n6. Regenerate pipeline when stack changes significantly.\n\n## References\n\n- [references\u002Fgithub-actions-templates.md](references\u002Fgithub-actions-templates.md)\n- [references\u002Fgitlab-ci-templates.md](references\u002Fgitlab-ci-templates.md)\n- [references\u002Fdeployment-gates.md](references\u002Fdeployment-gates.md)\n- [README.md](README.md)\n\n## Detection Heuristics\n\nThe stack detector prioritizes deterministic file signals over heuristics:\n\n- Lockfiles determine package manager preference\n- Language manifests determine runtime families\n- Script commands (if present) drive lint\u002Ftest\u002Fbuild commands\n- Missing scripts trigger conservative placeholder commands\n\n## Generation Strategy\n\nStart with a minimal, reliable pipeline:\n\n1. Checkout and setup runtime\n2. Install dependencies with cache strategy\n3. Run lint, test, build in separate steps\n4. Publish artifacts only after passing checks\n\nThen layer advanced behavior (matrix builds, security scans, deploy gates).\n\n## Platform Decision Notes\n\n- GitHub Actions for tight GitHub ecosystem integration\n- GitLab CI for integrated SCM + CI in self-hosted environments\n- Keep one canonical pipeline source per repo to reduce drift\n\n## Validation Checklist\n\n1. Generated YAML parses successfully.\n2. All referenced commands exist in the repo.\n3. Cache strategy matches package manager.\n4. Required secrets are documented, not embedded.\n5. Branch\u002Fprotected-environment rules match org policy.\n\n## Scaling Guidance\n\n- Split long jobs by stage when runtime exceeds 10 minutes.\n- Introduce test matrix only when compatibility truly requires it.\n- Separate deploy jobs from CI jobs to keep feedback fast.\n- Track pipeline duration and flakiness as first-class metrics.\n",{"name":5,"description":7},"main","c0a12fc98d85642fa8893e31fc5cf5dfad879de6","engineering\u002Fci-cd-pipeline-builder",0,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i","2026-03-13 21:49:18",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill ci-cd-pipeline-builder",{"tool":49,"command":50},"bunx","bunx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill ci-cd-pipeline-builder",{"tool":52,"command":53},"pnpm","pnpm dlx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill ci-cd-pipeline-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fci-cd-pipeline-builder\u002FSKILL.md",true,[57,63,67,71,75,81],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"README.md","REFERENCE","参考文档",1165,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fci-cd-pipeline-builder\u002FREADME.md",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fdeployment-gates.md",429,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fci-cd-pipeline-builder\u002Freferences\u002Fdeployment-gates.md",{"path":68,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fgithub-actions-templates.md",758,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fci-cd-pipeline-builder\u002Freferences\u002Fgithub-actions-templates.md",{"path":72,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fgitlab-ci-templates.md",476,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fci-cd-pipeline-builder\u002Freferences\u002Fgitlab-ci-templates.md",{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"scripts\u002Fpipeline_generator.py","SCRIPT","脚本",9676,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fci-cd-pipeline-builder\u002Fscripts\u002Fpipeline_generator.py",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"scripts\u002Fstack_detector.py",5778,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fci-cd-pipeline-builder\u002Fscripts\u002Fstack_detector.py",[86,113,139,168,188,211],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":31},"01M6DSNYM8PZKEXGYMRX53PVPH","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112],"risk","risk management specialist","management","risk management","risk analysis","risk evaluation","product","Evaluation","Production","lifecycle","analysis","user","use","risk matrix","Market","device","control","iso","medical","iso 14971",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":31},"01M6DSNSRBGVZWS23TK0ZQ52QC","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,111,138],"regulatory affairs head","regulatory","head","documentation","documents","packages","planning","devices","plan","access","write","strategy","evidence","standards","manage","intelligence","across","strategies","clinical",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":153,"publishedAt":31},"01M6DSNN7GNR2HZE66S4D31EP8","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[145,148],{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":149,"categoryName":150,"taxonomyType":151,"taxonomyTypeDesc":152},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[154,155,156,157,158,159,123,160,161,162,163,164,105,121,165,166,167,109,110,111],"quality manager qms iso13485","quality","design","review","support","workflows","audit","actions","compliance","system","process","up","maintenance","document",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":177,"publishedAt":31},"01M6DSNE5PQM106PM4EDGPBWGZ","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":151,"taxonomyTypeDesc":152},"01JBSEEDCAT000000000000037","律师与法务",[178,155,157,179,180,181,182,162,183,163,95,184,121,185,186,187,110],"quality manager qmr","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":198,"publishedAt":31},"01M6DSN7MYXB6X42TB1GH2TNSB","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[194,197],{"categoryNo":195,"categoryName":196,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":175,"categoryName":176,"taxonomyType":151,"taxonomyTypeDesc":152},[123,199,155,157,200,201,160,102,202,163,203,204,105,205,206,207,111,208,209,210],"quality documentation manager","workflow","change","document lifecycle","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":217,"publishedAt":31},"01M6DSN3R749H3R20K15QE8X8W","qms-audit-expert","ISO 13485 internal audit expertise for medical device QMS. Covers audit planning, execution, nonconformity classification, and CAPA verification. Use for internal audit planning, audit execution, finding classification, external audit preparation, or audit program management.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fqms-audit-expert\u002FSKILL.md",[],[160,218,219,126,220,221,222,223,95,105,224,108,110,111],"qms audit expert","expert","verification","execution","classification","schedule","checklist"]