ln-730-devops-setup
Coordinates Docker, CI/CD, and environment configuration setup via auto-detection
- License 许可
- MIT
- 最近更新
- 2026-05-02
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- ln-730-devops-setup
- license
- MIT
- description
- Coordinates Docker, CI/CD, and environment configuration setup via auto-detection
02 资源文件 10
- 参考文档agents/artifact-analyzer.md2.4 KB
- 参考文档agents/opportunity-reviewer.md1.7 KB
- 参考文档agents/skeptic-reviewer.md1.5 KB
- 参考文档agents/web-researcher.md1.6 KB
- 参考文档bmad-manifest.json496 B
- 参考文档prompts/contextual-discovery.md2.5 KB
- 参考文档prompts/draft-and-review.md3.9 KB
- 参考文档prompts/finalize.md3.8 KB
- 参考文档prompts/guided-elicitation.md3.3 KB
- 参考文档resources/brief-template.md2.3 KB
03 SKILL.md 正文
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.
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 Agent tool)
| Input: stack config, versions
| Output: Dockerfile.*, docker-compose.yml, .dockerignore
|
+---> ln-732-cicd-generator (via Agent tool)
| Input: stack config, detected commands
| Output: .github/workflows/ci.yml
|
+---> ln-733-env-configurator (via Agent 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
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.
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
Version: 1.1.0 Last Updated: 2026-01-10
04 同仓库更多 Skills
zarr-python
Chunked N-D arrays for cloud storage. Compressed arrays, parallel I/O, S3/GCS integration, NumPy/Dask/Xarray compatible, for large-scale scientific computing pipelines.
zabbix
Zabbix monitoring system automation via API and Python. Use when: (1) Managing hosts, templates, items, triggers, or host groups, (2) Automating monitoring configuration, (3) Sending data via Zabbix trapper/sender, (4) Querying historical data or events, (5) Bulk operations on Zabbix objects, (6) Maintenance window management, (7) User/permission management
x-twitter-growth
X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.
what-if-oracle
Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like "what if...", "what would happen if...", "what are the possibilities", "explore scenarios", "scenario analysis", "possibility space", "what could go wrong", "best case / worst case", "risk analysis", "contingency planning", "strategic options", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
venue-templates
Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.