generate-cicdlisted

# Generate CI/CD Workflows Generate GitHub Actions workflows through interactive conversation: analyze the repository, present findings, ask about workflow preferences, generate workflows based on confirmed choices. CI/CD involves **policy decisions** (PR vs direct push, release triggers, deployment strategy) that cannot be deduced from code alone. ## Key Rules - **Verify everything** before adding any step, secret, or config — examine the actual codebase. Ask when uncertain. - **Always present workflow choices** — even if tests and a Dockerfile are detected, the user decides when/how they run. - **Use project automation** over inline commands — call `npm test`, not `jest --coverage --ci`. See [references/best-practices.md](references/best-practices.md). - **GitHub Actions only** — if the user mentions a different CI platform, say so and stop. Otherwise proceed without asking about the platform. ## Process Execute sequentially. Each phase may change direction. Do NOT batch all questions upfront. ``` PHASE 1: ANALYZE → PHASE 2: PRESENT & ASK → PHASE 3: GENERATE ``` ### Step 1: Analyze Repository Analyze the entire repository — source code, automation, configs, docs, existing CI. 1. **Language/Framework** — Identify from source files and dependency manifests. Note version requirements. 2. **Existing Automation** — Find build/test/lint scripts and **read them to understand how they work** (arguments, setup, cleanup). If automation exists → use it. If not → ask user whe