Build or slim a repository's required commit build around fast product-behavior checks. Use when CI is slow, flaky, duplicated, or blocking on prose, naming, or file-layout linters, or when the user asks what should be required on every PR. Do not use for CD, release trains, or incident response.
Installs into .claude/skills of the current project.
Are you the author of Implement Continuous Integration?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/sylphxai-implement-continuous-integration)
---
name: implement-continuous-integration
description: "Build or slim a repository's required commit build around fast product-behavior checks. Use when CI is slow, flaky, duplicated, or blocking on prose, naming, or file-layout linters, or when the user asks what should be required on every PR. Do not use for CD, release trains, or incident response."
---
# Implement Continuous Integration
A required check is useful when red names a real product, build, security, or public-contract defect a human can fix in product code. Retire wording, naming, and layout scans from the required path. Flakes on the required path are product defects, not weather.
Open [industry commit build](references/industry-commit-build.md) when classifying an existing suite or parking a slow check.
