ln-730-devops-setup
Sets up Docker, CI/CD, and environment configuration with auto-detection. Use when adding DevOps infrastructure to a project.
- Installs
- 394
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-730-devops-setup- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads ln-730-devops-setup automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Paths: File paths (
references/,../ln-*) are relative to this skill directory.
ln-730-devops-setup
Type: L2 Domain Coordinator Category: 7XX Project Bootstrap Parent: ln-700-project-bootstrap
Coordinates DevOps infrastructure setup by delegating to specialized workers.
Purpose & Scope
Orchestrates the complete DevOps setup for a project:
- Does: Auto-detect stack, delegate to workers, verify configuration
- Does NOT: Generate files directly (delegates to ln-731, ln-732, ln-733)
Overview
| Aspect | Details |
|---|---|
| Input | Project directory with source code |
| Output | Docker, CI/CD, environment configuration |
| Workers | ln-731 (Docker), ln-732 (CI/CD), ln-733 (Environment) |
| Mode | Auto-detect (no user prompts) |
Supported Stacks
| Component | Option 1 | Option 2 |
|---|---|---|
| Frontend | React/Vite + Nginx | - |
| Backend | .NET 8/9 | Python (FastAPI/Django) |
| Database | PostgreSQL | - |
| CI/CD | GitHub Actions | - |
Workflow
Phase 1: Pre-flight Validation
Check required tools and project structure:
- Verify Docker is installed (
docker --version) - Verify docker-compose is available
- Check for existing DevOps files (warn if overwriting)
Output: Validation report or STOP with instructions
Phase 2: Project Analysis (Auto-detect)
Detect project stack automatically:
| Detection | Method | Files to Check |
|---|---|---|
| Frontend | Package.json presence | src/frontend/package.json, package.json |
| Backend .NET | .csproj/.sln presence | *.sln, src/**/*.csproj |
| Backend Python | requirements.txt/pyproject.toml | requirements.txt, pyproject.toml |
| Database | Connection strings in code | appsettings.json, .env.example |
| Existing CI/CD | Workflow files | .github/workflows/, azure-pipelines.yml |
Version Detection:
- Node.js: Read from
package.jsonengines or usenode -v - .NET: Read from
*.csprojTargetFramework - Python: Read from
pyproject.tomlorruntime.txt - PostgreSQL: Default to latest stable (17)
Output: Stack configuration object with detected versions
Phase 3: Worker Delegation
Delegate to workers in parallel (independent tasks):
ln-730 (Coordinator)
|
+---> ln-731-docker-generator (via Skill tool)
| Input: stack config, versions
| Output: Dockerfile.*, docker-compose.yml, .dockerignore
|
+---> ln-732-cicd-generator (via Skill tool)
| Input: stack config, detected commands
| Output: .github/workflows/ci.yml
|
+---> ln-733-env-configurator (via Skill tool)
Input: detected environment variables
Output: .env.example, .env.development, .gitignore updates
Error Handling:
- If worker fails, log error and continue with others
- Report all failures at the end
- Suggest manual fixes for failed components
Invocations:
Skill(skill: "ln-731-docker-generator", args: "{projectPath}")
Skill(skill: "ln-732-cicd-generator", args: "{projectPath}")
Skill(skill: "ln-733-env-configurator", args: "{projectPath}")
Phase 4: Configuration Verification
Verify generated configuration:
- Run
docker-compose configto validate syntax - Check all referenced files exist
- Verify no secrets in committed files
Output: Verification report
Phase 5: Completion Report
Generate summary:
- List all created files
- Show detected stack configuration
- Provide next steps for user
Generated Files
Docker (ln-731)
Dockerfile.frontend- Multi-stage build for frontendDockerfile.backend- Multi-stage build for backenddocker-compose.yml- Service orchestrationdocker-compose.override.yml- Development overrides (optional).dockerignore- Build context exclusions
CI/CD (ln-732)
.github/workflows/ci.yml- Main CI pipeline
Environment (ln-733)
.env.example- Template with all variables.env.development- Development defaults.env.production- Production template (placeholders).gitignoreupdates - Secrets protection
Critical Notes
- Auto-detect Only: No interactive prompts. Uses detected values or sensible defaults.
- Idempotent: Check file existence before creation. Warn before overwriting.
- Parallel Execution: Workers are independent, can run in parallel.
- Error Recovery: Continue on partial failures, report all issues at end.
- Version Pinning: Use detected versions, not hardcoded values.
TodoWrite format (mandatory):
- Invoke ln-731-docker-generator (pending)
- Invoke ln-732-cicd-generator (pending)
- Invoke ln-733-env-configurator (pending)
- Verify configuration (pending)
- Generate completion report (pending)
Worker Invocation (MANDATORY)
Host Skill Invocation: Skill(skill: "...", args: "...") is mandatory delegation.
- Claude: call the Skill tool exactly as shown.
- Codex: if no Skill tool exists, locate the named skill in available skills, read its
SKILL.md, treatargsas$ARGUMENTS, execute that skill workflow, then return here with its result/artifact. - Do not inline worker logic or mark the worker complete without executing the target skill.
| Phase | Worker | Context |
|---|---|---|
| 3a | ln-731-docker-generator | Shared (Skill tool) — Dockerfiles, docker-compose, .dockerignore |
| 3b | ln-732-cicd-generator | Shared (Skill tool) — CI/CD pipeline configuration |
| 3c | ln-733-env-configurator | Shared (Skill tool) — environment files and .gitignore |
All workers: Invoke via Skill tool — workers see coordinator context.
Definition of Done
- Pre-flight validation passed
- Stack auto-detected successfully
- All workers completed (or failures documented)
-
docker-compose configvalidates successfully - No secrets in generated files
- Completion report displayed
Reference Files
- Worker:
../ln-731-docker-generator/SKILL.md - Worker:
../ln-732-cicd-generator/SKILL.md - Worker:
../ln-733-env-configurator/SKILL.md
Meta-Analysis
Optional reference: load references/meta_analysis_protocol.md only when the user asks for post-run meta-analysis or protocol-formatted run reflection.
Skill type: execution-orchestrator. When requested, run after all phases complete. Output to chat using the execution-orchestrator format.
Version: 1.1.0 Last Updated: 2026-01-10
FAQ
What does the ln-730-devops-setup skill do?
Sets up Docker, CI/CD, and environment configuration with auto-detection. Use when adding DevOps infrastructure to a project.
How do I install ln-730-devops-setup?
Run npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-730-devops-setup in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ln-730-devops-setup/ (personal) or .claude/skills/ln-730-devops-setup/ (project).
Which AI agents can use ln-730-devops-setup?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is ln-730-devops-setup safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains ln-730-devops-setup?
It is published by levnikolaevich in levnikolaevich/claude-code-skills. It has 394 recorded installs.
More from levnikolaevich/claude-code-skills
ln-100-documents-pipeline
levnikolaevich/claude-code-skills
Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.
ln-620-codebase-auditor
levnikolaevich/claude-code-skills
Open the skill to read its SKILL.md instructions.
ln-775-api-docs-generator
levnikolaevich/claude-code-skills
Configures Swagger/OpenAPI documentation for backend APIs. Use when adding interactive API docs to a project.
ln-624-code-quality-auditor
levnikolaevich/claude-code-skills
Checks cyclomatic complexity, nesting, long methods, god classes, O(n2), N+1 queries, constants management. Use when auditing code quality.
ln-782-test-runner
levnikolaevich/claude-code-skills
Executes all test suites and reports results with coverage. Use when verifying that test infrastructure works after bootstrap.
ln-634-test-coverage-auditor
levnikolaevich/claude-code-skills
Open the skill to read its SKILL.md instructions.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.