skills.rest
jsamuelsen11
jsamuelsen11COMMUNITY
Explore all skills by this author →
GitHub

actions-conventions

Standardize GitHub Actions workflow naming, permissions, and structure.

Updated Feb 7, 2026
Search Tags:#security#conventions#best-practices#github-actions#ci-cd#workflows
One-click install
npx skills add https://github.com/jsamuelsen11/claude-config --skill actions-conventions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: actions-conventions
Source: https://github.com/jsamuelsen11/claude-config/tree/main/plugins/ccfg-github-actions/skills/actions-conventions
Command: npx skills add https://github.com/jsamuelsen11/claude-config --skill actions-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub Actions conventions standardize workflow design to improve consistency, security, and maintainability across repositories.

Core Features & Use Cases

  • Enforces descriptive workflow naming, explicit permissions, structured jobs, and clear step naming for predictable automation.
  • Guides secure and reliable CI/CD pipelines, deployment workflows, and governance across teams.
  • Provides a framework for evaluating and refactoring existing workflows to align with best practices.

Quick Start

Follow the conventions to refactor or create a new workflow that clearly adheres to naming, permissions, and structure guidelines.

Frequently Asked Questions about actions-conventions

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

FAQPage Schema
What are the best practices for securing GitHub Actions workflows?▼

Securing GitHub Actions workflows requires applying explicit permissions, consistent naming conventions, and structured job organization. This standardizes workflow design to improve reliability and security across your CI/CD pipelines and repositories.

How do I standardize GitHub Actions naming conventions across multiple repositories?▼

You can standardize GitHub Actions naming conventions by applying guidelines for descriptive workflow naming, clear step descriptions, and structured jobs. This ensures predictable automation and maintainable CI/CD pipelines across teams and projects.

How do I refactor existing CI/CD workflows to align with GitHub Actions best practices?▼

Refactoring existing CI/CD workflows involves evaluating them against conventions for explicit permissions, naming, and trigger configuration. This provides a framework to update workflows for improved consistency and security.

Why do my GitHub Actions workflows lack consistent permissions and structure?▼

GitHub Actions workflows lack consistent permissions and structure when they do not follow standardized conventions. Imposing explicit permissions and robust workflow organization guidelines solves this by enforcing predictable automation across repositories.

Related Skills

Explore More Software Engineering Skills→
KentoShimizuKentoShimizu
7

github-actions-workflow-design

Design GitHub Actions workflows with explicit triggers and least-privilege permissions.

Community
Intermediate
BagelHoleBagelHole
46

github-actions

Automates CI/CD workflows with GitHub Actions for build, test, and deployment processes.

Community
Intermediate
beomeodevbeomeodev

ms-foundation-ears

Validate requirements against EARS patterns and detect forbidden phrases.

Community
Advanced
windyskywindysky

moai-ref-git-workflow

Provide standardized git workflow patterns, branch strategies, and PR templates.

Community
Advanced