ln-732-cicd-generator
Scannednpx machina-cli add skill levnikolaevich/claude-code-skills/ln-732-cicd-generator --openclawPaths: File paths (
shared/,references/,../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.
ln-732-cicd-generator
Type: L3 Worker Category: 7XX Project Bootstrap Parent: ln-730-devops-setup
Generates GitHub Actions CI pipeline for automated testing and validation.
Purpose & Scope
Creates CI/CD workflow for GitHub:
- Does: Generate .github/workflows/ci.yml with lint, test, build, docker jobs
- Does NOT: Configure deployment, manage secrets, set up CD pipelines
Inputs
| Input | Source | Description |
|---|---|---|
| Stack Type | ln-730 coordinator | backend-dotnet, backend-python |
| Versions | Auto-detected | Node.js, .NET or Python versions |
| Frontend Path | Auto-detected | Path to frontend directory |
| Build Commands | Auto-detected | npm scripts, dotnet/pytest commands |
Outputs
| File | Purpose | Template |
|---|---|---|
.github/workflows/ci.yml | Main CI pipeline | github_ci_dotnet.template.yml or github_ci_python.template.yml |
Workflow
Phase 1: Stack Analysis
Determine which template to use:
| Detection | Backend Template |
|---|---|
.sln or .csproj present | github_ci_dotnet.template.yml |
requirements.txt or pyproject.toml present | github_ci_python.template.yml |
Detect commands:
- Frontend: Read scripts from package.json (lint, build, test)
- .NET: Standard dotnet restore/build/test
- Python: pip install, ruff lint, pytest
Phase 2: Variable Substitution
Replace template variables:
| Variable | Source | Default |
|---|---|---|
{{NODE_VERSION}} | package.json engines | 22 |
{{DOTNET_VERSION}} | *.csproj TargetFramework | 9.0.x |
{{PYTHON_VERSION}} | pyproject.toml | 3.12 |
{{FRONTEND_PATH}} | Directory detection | src/frontend |
Phase 3: Directory Creation
Create .github/workflows/ directory if not exists.
Phase 4: File Generation
Generate ci.yml from selected template:
- Check if workflow already exists (warn before overwrite)
- Apply variable substitution
- Write to
.github/workflows/ci.yml - Validate YAML syntax
Generated Pipeline Structure
Jobs Overview
| Job | Purpose | Dependencies |
|---|---|---|
| frontend | Lint, build, test React/Vite | None |
| backend | Build, test .NET or Python | None |
| docker | Build images, health checks | frontend, backend |
Frontend Job Steps
- Checkout code
- Setup Node.js with caching
- Install dependencies (
npm ci) - Run linter (
npm run lint) - Build application (
npm run build) - Run tests (
npm test)
Backend Job Steps (.NET)
- Checkout code
- Setup .NET SDK
- Restore dependencies (
dotnet restore) - Build (
dotnet build) - Run tests (
dotnet test)
Backend Job Steps (Python)
- Checkout code
- Setup Python with pip caching
- Install dependencies (
pip install -r requirements.txt) - Run linter (
ruff check) - Run tests (
pytest)
Docker Job Steps
- Checkout code
- Build images (
docker compose build) - Start containers (
docker compose up -d) - Wait for startup (30 seconds)
- Health check frontend (port 3000)
- Health check backend (port 5000/8000)
- Show logs on failure
- Stop containers (
docker compose down)
Triggers
| Event | Branches |
|---|---|
| Push | main, develop |
| Pull Request | main |
Best Practices Applied
| Practice | Implementation |
|---|---|
| Dependency caching | npm cache, pip cache |
| Pinned versions | actions/checkout@v4, setup-node@v4 |
| Parallel jobs | frontend and backend run in parallel |
| Fail fast | docker job waits for both to succeed |
| Clean up | docker compose down runs always |
| Debug support | logs shown on failure |
Quality Criteria
Generated workflow must:
- Pass YAML syntax validation
- Use pinned action versions (not
@latest) - Include dependency caching
- Have health checks for docker job
- Clean up resources on completion
Critical Notes
- GitHub Actions Only: This skill generates only GitHub Actions workflows. No Azure/GitLab support.
- Template-based: Use templates from references/. Do NOT hardcode workflow contents.
- Idempotent: Check if .github/workflows/ exists. Warn before overwriting ci.yml.
- Version Detection: Use detected versions, not hardcoded defaults.
Reference Files
| File | Purpose |
|---|---|
| github_ci.template.yml | Full template with comments |
| github_ci_dotnet.template.yml | Compact .NET stack template |
| github_ci_python.template.yml | Compact Python stack template |
Version: 1.1.0 Last Updated: 2026-01-10
Source
git clone https://github.com/levnikolaevich/claude-code-skills/blob/master/ln-732-cicd-generator/SKILL.mdView on GitHub Overview
ln-732-cicd-generator automatically creates a GitHub Actions CI pipeline by generating .github/workflows/ci.yml. It selects the correct template based on the project stack (dotnet or Python) and wires lint, tests, build, and docker jobs. It intentionally excludes deployment, secret management, or CD setup.
How This Skill Works
It analyzes the repository to choose the correct CI template (dotnet or python) and detects commands for linting, building, and testing. It then substitutes variables (NODE_VERSION, DOTNET_VERSION, PYTHON_VERSION, FRONTEND_PATH), creates the workflows directory if needed, and writes a validated ci.yml from the selected template.
When to Use It
- You need a reproducible CI pipeline for a repo with backend-dotnet or backend-python and an auto-detected frontend path.
- Setting up CI after adding GitHub Actions to a new project.
- You want to enforce caching of dependencies (npm/pip) and pinned action versions.
- You manage a mono-repo (frontend + backend) and want a single ci.yml to cover lint, tests, and docker.
- You require automatic template selection based on project files (.sln/.csproj or requirements.txt/pyproject.toml).
Quick Start
- Step 1: Ensure the repo contains detectable files (package.json with engines, pyproject.toml, or a .csproj/.sln) so the generator can determine the stack.
- Step 2: Run the ln-732-cicd-generator to produce .github/workflows/ci.yml from the appropriate template.
- Step 3: Commit and push to trigger GitHub Actions; adjust variables or paths if needed.
Best Practices
- Dependency caching for npm and pip to speed up builds
- Pin actions to stable versions (e.g., actions/checkout@v4)
- Run frontend, backend, and docker steps in parallel when possible
- Validate YAML syntax and guard against overwriting existing workflows
- Auto-detect stack and adapt CI template to avoid misconfiguration
Example Use Cases
- Mono-repo with React frontend, .NET backend, and Python services using a single ci.yml
- Python-based microservice with pytest and ruff lint
- .NET Core API with Dockerized build and health checks
- Frontend with npm scripts for lint/build/test and backend with dotnet test
- Teams migrating from custom pipelines to generated GitHub Actions workflows