Imported from majiayu000/claude-skill-registry-data (devops/ci-cd-compliance/SKILL.md). Install upstream with npx skills add majiayu000/claude-skill-registry-data --skill ci-cd-compliance. Copyright stays with the author.

CI/CD Compliance Rules

Name: ci-cd-compliance
Author: majiayu000

CI Gates Sequence

install → lint/format → typecheck → unit → integration → (optional e2e) → package

Merge Policy

Merge only if green
Auto-deploy to staging on merge
Production requires tag/approval

CI Failure Handling

When CI fails:

Explain root cause in PR comment
Include the fix in the same PR when feasible
Don't merge until all gates pass

IDE Integration

AINative / Windsurf / Cursor / Claude Code: Use built-in code actions and terminal to run tests/linters
Prefer unified diffs in responses so changes are patchable across IDEs
Attach artifacts (test output, screenshots, logs) whenever you assert a claim

Reference Files

See references/pipeline-requirements.md for detailed CI configuration, gate definitions, and failure debugging guide.

{ "ocm": "1", "id": "majiayu000-claude-skill-registry-data-ci-cd-compliance", "kind": "skill", "name": "ci-cd-compliance", "description": "CI/CD pipeline requirements and deployment standards. Use when (1) Setting up CI/CD pipelines, (2) Debugging CI failures, (3) Configuring deployment workflows, (4) Managing staging/production releases, (5) Investigating build failures. Covers CI gate requirements, merge policies, auto-deploy to staging, production approval process.", "publisher": "majiayu000", "version": "1.0.0", "capabilities": { "domains": [ "legal" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "CI/CD pipeline requirements and deployment standards. Use when (1) Setting up CI/CD pipelines, (2) Debugging CI failures, (3) Configuring deployment workflows, (4) Managing staging/production releases, (5) Investigating build failures. Covers CI gate requirements, merge policies, auto-deploy to staging, production approval process." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/majiayu000/claude-skill-registry-data", "path": "devops/ci-cd-compliance/SKILL.md", "ref": "f863c11651055f498e1466492dc2a0d95721d2d5", "url": "https://github.com/majiayu000/claude-skill-registry-data/blob/f863c11651055f498e1466492dc2a0d95721d2d5/devops/ci-cd-compliance/SKILL.md", "key": "majiayu000/claude-skill-registry-data/devops/ci-cd-compliance/SKILL.md" } }, "instructions": "# CI/CD Compliance Rules\n\n## CI Gates Sequence\n\n**install → lint/format → typecheck → unit → integration → (optional e2e) → package**\n\n## Merge Policy\n\n* **Merge only if green**\n* Auto-deploy to **staging** on merge\n* Production requires tag/approval\n\n## CI Failure Handling\n\nWhen CI fails:\n1. **Explain root cause** in PR comment\n2. **Include the fix** in the same PR when feasible\n3. Don't merge until all gates pass\n\n## IDE Integration\n\n* **AINative / Windsurf / Cursor / Claude Code:** Use built-in code actions and terminal to run tests/linters\n* Prefer **unified diffs** in responses so changes", "cost": { "context_tokens": 211 } }

ci-cd-compliance

About

CI/CD Compliance Rules

CI Gates Sequence

Merge Policy

CI Failure Handling

IDE Integration

Reference Files

Use it

Manifest

Reviews