Loading...
Loading...
Found 248 Skills
Check GitHub Actions workflow status after git push using gh CLI. Reports CI status, identifies failing jobs, and suggests local reproduction commands. Use after "git push", when user asks about CI status, workflow failures, or build results. Use for "check CI", "workflow status", "actions failing", or "build broken". Do NOT use for local linting (use code-linting), debugging test failures locally (use systematic-debugging), or setting up new workflows.
Create and audit GitHub Actions workflows with SHA pinning, permissions, and caching checks. Use when adding CI/CD, reviewing workflow files, or fixing action pinning.
GitHub Actions workflow security, performance optimization, and best practices
Guides users through setting up Tauri GitHub Actions CI/CD pipelines and workflows for automated building, testing, and releasing cross-platform desktop applications.
CI/CD automation and workflow orchestration using GitHub Actions for builds, tests, deployments, and repository automation
GitHub Actions CI/CD workflows for automating build, test, and deployment
Build production CI/CD pipelines with GitHub Actions. Implements matrix builds, caching, deployments, testing, security scanning. Use for automated testing, deployments, release workflows. Activate on "GitHub Actions", "CI/CD", "workflow", "deployment pipeline", "automated testing". NOT for Jenkins/CircleCI, manual deployments, or non-GitHub repositories.
GitHub Actions 2025 features including 1 vCPU runners, immutable releases, and Node24 migration
Comprehensive toolkit for validating, linting, and testing GitHub Actions workflow files, custom local actions, and public actions. Use this skill when working with GitHub Actions YAML files (.github/workflows/*.yml), validating workflow syntax, testing workflow execution with act, or debugging workflow issues.
Scaffold a traditional deterministic GitHub Actions CI/CD workflow. Use this when creating build, test, deploy, lint, release, or security scan pipelines. This is distinct from agentic workflows — no AI is involved at runtime.
Create and configure GitHub Actions. Use when building custom actions, setting up runners, implementing security practices, or publishing to the marketplace.
Update GitHub Actions versions in workflow files, focusing only on major version changes. Use when the user wants to update action versions, check for outdated GitHub Actions, or upgrade workflow dependencies to their latest major versions.