.claude/skills/ln-732-cicd-generator/SKILL.md
Generates GitHub Actions CI workflow configuration
npx skillsauth add cbbkrd-tech/jl-finishes ln-732-cicd-generatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Paths: 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.
Type: L3 Worker Category: 7XX Project Bootstrap Parent: ln-730-devops-setup
Generates GitHub Actions CI pipeline for automated testing and validation.
Creates CI/CD workflow for GitHub:
| 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 |
| File | Purpose | Template |
|------|---------|----------|
| .github/workflows/ci.yml | Main CI pipeline | github_ci_dotnet.template.yml or github_ci_python.template.yml |
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:
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 |
Create .github/workflows/ directory if not exists.
Generate ci.yml from selected template:
.github/workflows/ci.yml| Job | Purpose | Dependencies | |-----|---------|--------------| | frontend | Lint, build, test React/Vite | None | | backend | Build, test .NET or Python | None | | docker | Build images, health checks | frontend, backend |
npm ci)npm run lint)npm run build)npm test)dotnet restore)dotnet build)dotnet test)pip install -r requirements.txt)ruff check)pytest)docker compose build)docker compose up -d)docker compose down)| Event | Branches | |-------|----------| | Push | main, develop | | Pull Request | main |
| 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 |
Generated workflow must:
@latest)| 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
testing
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.
development
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
development
Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences.
development
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' or 'involuntary churn.' This skill covers voluntary churn (cancel flows, save offers, exit surveys) and involuntary churn (dunning, payment recovery). For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.