GitHub Actions Workflow Builder
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task. # Context - Pack: Developers & Tech Professionals - Category: DevOps & CI/CD - Use case: GitHub Actions Workflow Builder - Source task: - Write a GitHub Actions workflow for {{describe_the_workflow}}. Include: - 1. trigger conditions (push, PR, schedule, manual) - 2. job structure with parallelism where applicable - 3. caching for dependencies - 4. secrets usage (how to reference without hardcoding) - 5. matrix builds for multiple versions/environments - 6. notification on failure (Slack or email) # Goal A complete GitHub Actions YAML with triggers, parallel jobs, dependency caching, secrets handling, matrix builds, and failure notifications. # Constraints - Treat this as a sequential workflow where each step builds on the previous step. - Keep every step clearly labeled and easy to run separately if needed. - Avoid generic filler, vague advice, and unsupported claims. - Make the output specific, practical, and ready to use. # Output A complete GitHub Actions YAML with triggers, parallel jobs, dependency caching, secrets handling, matrix builds, and failure notifications.
{{double-curly}} with your real context.GitHub Actions Workflow Builder
Cache your dependency install step — a cached npm install or pip install can reduce workflow time from 3 minutes to 20 seconds.
Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.
Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.
Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.
Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.