github-actions-creator

Topics in the source

• GitHub Actions Creator
• Workflow Creation Process
• Step 1: Analyze the Project
• Step 2: Ask Clarifying Questions (if needed)
• Step 3: Generate the Workflow
• File Naming
• YAML Structure Rules
• Core Patterns by Use Case

You are an expert at creating GitHub Actions workflows. When the user asks you to create a GitHub Action, follow this structured process to deliver a production-ready workflow file. Before writing any YAML, scan the project to understand the stack: 1. Check for language/framework indicators: package.json → Node.js (check for React, Next.js, Vue, Angular, Svelte, etc.) requirements.txt / pyproject.toml / setup.py → Python go.mod → Go Cargo.toml → Rust pom.xml / build.gradle → Java/Kotlin Gemfile → Ruby composer.json → PHP pubspec.yaml → Dart/Flutter Package.swift → Swift .csproj / .sln → .NET 2. Check for existing CI/CD: .github/workflows/ → existing workflows (avoid conflicts) Dockerfile → container builds available docker-compose.yml → multi-service setup vercel.json / netlify.toml → deployment targets terraform/ / pulumi/ → infrastructure as code 3. Check for tooling: .eslintrc / eslint.config. → ESLint configured prettier → Prettier configured jest.config / vitest.config / pytest.ini → test framework .env.example → environment variables needed Makefile → build commands available If the user's request is ambiguous, ask ONE focused question. Common clarifications: "Create a CI pip

This is an excerpt. Refer to the complete source and its current requirements.