ln-732-cicd-generator
Generates GitHub Actions CI workflow configuration. Use when adding continuous integration to a project.
- License 许可
- MIT
- 最近更新
- 2026-06-15
- Stars
- ★ 2
- Forks
- 1
01 前言 Front Matter
- name
- ln-732-cicd-generator
- model
- claude-sonnet-4-6
- license
- MIT
- description
- Generates GitHub Actions CI workflow configuration. Use when adding continuous integration to a project.
02 资源文件 3
- 参考文档references/github_ci_dotnet.template.yml1.5 KB
- 参考文档references/github_ci_python.template.yml1.7 KB
- 参考文档references/github_ci.template.yml4.7 KB
03 SKILL.md 正文
Paths: File paths (
references/,../ln-*) are relative to this skill directory.
ln-732-cicd-generator
Type: L3 Worker Category: 7XX Project Bootstrap
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 |
Definition of Done
- [ ]
.github/workflows/ci.ymlgenerated and passes YAML validation - [ ] Pipeline includes lint, build, test, and docker jobs
- [ ] All action versions pinned (not
@latest)
Version: 1.1.0 Last Updated: 2026-01-10
04 同仓库更多 Skills
solana-dev
Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "deploy to devnet", or "explain Solana concepts" (rent, accounts, PDAs, CPIs, etc.). End-to-end Solana development playbook covering wallet connection, Anchor/Pinocchio programs, Codama client generation, LiteSVM/Mollusk/Surfpool testing, and security checklists. Integrates with the Solana MCP server for live documentation search. Prefers framework-kit (@solana/client + @solana/react-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana/kit for client/RPC code, and @solana/web3-compat for legacy boundaries.
generating-trading-signals
Generate trading signals using technical indicators (RSI, MACD, Bollinger Bands, etc.). Combines multiple indicators into composite signals with confidence scores. Use when analyzing assets for trading opportunities or checking technical indicators. Trigger with phrases like "get trading signals", "check indicators", "analyze for entry", "scan for opportunities", "generate buy/sell signals", or "technical analysis".
prediction-monitor
Prediction Monitor - Auto-activating skill for ML Deployment. Triggers on: prediction monitor, prediction monitor Part of the ML Deployment skill category.
strategy-advisor
High-level strategic thinking and business decision guidance for planning and direction-setting. Use when: making strategic decisions, evaluating business options, setting direction, analyzing trade-offs, or when user mentions strategy, business planning, competitive analysis, or long-term planning.
app-paywall-pilot
Design, audit, debug, and implement App Store-compliant mobile paywalls, subscription flows, pricing screens, trials, offers, feature gates, and subscription lifecycle UX. Use when the user asks to audit my paywall, fix App Store 3.1.2 rejection, improve trial-to-paid, choose plans/prices/trials, review RevenueCat/Adapty/Apphud/Superwall setup, calculate LTV/ROAS, or build paywall implementation.
figma
Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.