make-github-actions-workflow

Create and configure GitHub Actions workflow YAML files under .github/workflows.

14.8k|3.4k|Updated Jan 23, 2014

Search Tags:#automation #security #github #yaml #workflows #ci #pr-management

Ready to run

npx skills add https://github.com/dotnet/efcore --skill make-github-actions-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: make-github-actions-workflow
Source: https://github.com/dotnet/efcore/tree/main/.agents/skills/make-github-actions-workflow
Command: npx skills add https://github.com/dotnet/efcore --skill make-github-actions-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and configure GitHub Actions workflows to automate CI validation, PR handling, and workflow governance across repositories, reducing repetitive setup and human error.

Core Features & Use Cases

Workflow scaffolding: Create and organize workflow YAML files in .github/workflows with kebab-case names.
Convention enforcement: Apply repository-wide conventions (runners, permissions, naming) consistently.
Safety & troubleshooting: Provide guardrails and validation to prevent misconfigurations and insecure patterns.
Use Case: Standardize CI pipelines, PR validation, and notification workflows across multiple repos.

Quick Start

Create a new workflow under .github/workflows following the repository conventions and name it descriptively.

Frequently Asked Questions about make-github-actions-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a GitHub Actions workflow for CI automation?▼

To create a GitHub Actions CI workflow, generate a YAML file under .github/workflows/ using a descriptive kebab-case name. This workflow scaffolding process standardizes runners and permissions to automate continuous integration validation consistently.

How do I enforce permissions and naming conventions across GitHub Actions workflows?▼

Enforce GitHub Actions conventions by applying repository-wide rules for explicit permissions, kebab-case file naming, and default runners. This convention enforcement prevents insecure patterns and reduces misconfiguration errors across multiple repositories.

Can I use actions/github-script to add custom logic to my PR validation workflow?▼

Yes, you can use actions/github-script to add script-based logic to your PR validation workflow. This supports PR automation and workflow governance by allowing custom validation scripts directly within your GitHub Actions YAML configuration.

What is the default runner used when scaffolding GitHub Actions workflows?▼

The default runner used when scaffolding GitHub Actions workflows is ubuntu-latest. This standardization ensures consistent CI validation environments and applies repository-wide conventions for automated PR handling and workflow governance across repositories.

How do I troubleshoot insecure patterns in my GitHub Actions YAML configuration?▼

Troubleshoot insecure GitHub Actions YAML by validating explicit permissions declarations and checking for misconfigurations. Safety guardrails and validation checks provide repository-wide workflow governance to prevent insecure patterns and standardize CI pipelines.

Do I need to manually place workflow files in specific directories for GitHub Actions?▼

Yes, GitHub Actions requires placing workflow YAML files under the .github/workflows/ directory. Automating this placement ensures workflows follow repository conventions for CI, PR automation, and consistent workflow governance across repositories.