cicd

Automate GitHub Actions CI governance with validation gates and explicit permissions.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/oornnery/skills --skill cicd-oornnery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cicd
Source: https://github.com/oornnery/skills/tree/main/skills/cicd
Command: npx skills add https://github.com/oornnery/skills --skill cicd-oornnery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

GitHub Actions CI guidance to implement validation gates, workflow permissions, matrices, caching, path filters, artifacts, and workflow verification to keep CI green and auditable.

Core Features & Use Cases

  • Provides a blueprint for explicit permissions and minimal privilege in workflows.
  • Guides safe caching, parallel jobs, and matrix strategies to optimize CI time.
  • Offers verification techniques with tools like actionlint and act to ensure workflow reliability and auditability.

Quick Start

Scaffold a repo-aligned GitHub Actions workflow that enforces explicit permissions and validates code early.

Frequently Asked Questions about cicd

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

FAQPage Schema
How do I set up GitHub Actions CI workflows with explicit permissions and least privilege?

GitHub Actions CI workflows enforce least privilege by declaring explicit permissions in YAML templates, restricting token access to only required resources. This ensures pipelines remain secure and auditable across multiple branches.

What is the best way to optimize GitHub Actions CI time using matrix builds and caching?

Optimizing GitHub Actions CI time involves configuring matrix builds for parallelization and implementing safe caching strategies. This approach runs jobs concurrently across branches, significantly reducing validation gate durations.

How do I validate GitHub Actions workflows for reliability before pushing to production?

Validating GitHub Actions workflows for reliability uses tools like actionlint and act to verify configurations locally. This ensures your CI pipelines remain deterministic and auditable before integration.

Can I use path filters in GitHub Actions to trigger CI pipelines only for specific file changes?

Yes, you can use path filters in GitHub Actions to trigger CI pipelines only when specific files change. This configuration reduces unnecessary workflow runs and optimizes validation gate execution.

How do I manage auditable artifacts in GitHub Actions CI workflows?

Managing auditable artifacts in GitHub Actions CI workflows involves configuring YAML templates to generate and store verified build outputs. This ensures deterministic tool configuration and traceable validation across pipeline runs.

Does GitHub Actions CI support deterministic tool configuration for consistent pipeline execution?

Yes, GitHub Actions CI supports deterministic tool configuration through standard tooling and YAML templates. This ensures consistent pipeline execution and reliable validation gates across different environments and branches.