github-workflows

Create and review GitHub Actions workflows for CI, releases, and image publishing.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill github-workflows-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-workflows
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/github-workflows
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill github-workflows-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Writing GitHub Actions workflows from scratch often leads to inconsistent conventions, overly broad permissions, unsafe trigger patterns, and release pipelines that skip critical verification steps. This Skill applies repository-native GitHub Actions patterns so workflows are scoped, least-privilege, and aligned with existing monorepo conventions. ## Core Features & Use Cases - Service-scoped CI workflows: Generate PR, push, and manual-dispatch CI with paths filters, project-prefixed names, minimal permissions, and concurrency controls. - Release and image publication: Create tag-driven GitHub Release workflows and container image publish workflows with tag lineage checks, immutable tags, SBOM, provenance, and digest manifests. - Bot-safe merge automation: Build Dependabot auto-merge workflows that scope by actor and changed files without executing untrusted PR code. - Use Case: You are adding a new Python service to a monorepo and need PR CI, a tag-driven release workflow, and an image publish workflow. The Skill renders all three from templates, aligned with repo conventions and validated locally. ## Quick Start Ask the agent to use the github-workflows skill to create a PR CI workflow and a tag-driven release workflow for your service directory.

Frequently Asked Questions about github-workflows

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

FAQPage Schema
How do I create a GitHub Actions CI workflow for a monorepo service?

Scope the workflow with paths filters for the service directory and the workflow file itself, use project-prefixed workflow and job names, set defaults.run.working-directory for service-local commands, and keep permissions at contents: read with concurrency cancellation enabled.

How do I set up a tag-driven GitHub Release workflow?

Trigger on tags matching <project>-vMAJOR.MINOR.PATCH, check out full history, resolve the tagged commit with git rev-list, verify it belongs to the release branch, rebuild and version-check the artifact, and generate release notes from CHANGELOG.md, failing if the section is missing or empty.

Is pull_request_target safe for Dependabot auto-merge workflows?

pull_request_target is acceptable only when the workflow never checks out or executes untrusted PR code. Pass dynamic values through step-level env instead of embedding them in run blocks, and restrict auto-merge by both actor and changed-file scope.

What permissions should a GitHub Actions workflow use?

Start from least privilege: contents: read for CI workflows, and grant contents: write or pull-requests: write only to workflows that actually publish releases, approve, label, or merge. Declare permissions explicitly on every workflow.

How do I publish container images with immutable tags in GitHub Actions?

Use Docker Buildx with GitHub Actions cache, emit tags like sha-<shortsha> and X.Y.Z-g<shortsha>, enable provenance mode=max and sbom: true, verify tag commits belong to the main branch, and record the pushed digest in a manifest artifact and step summary.

When should I not use this workflow skill?

Do not use it to design container images or runtime contracts, which belong to the container skill, or to execute registry releases, which belong to publish-image. It owns only the GitHub Actions YAML orchestration layer.