publish-image

Publishes container image releases end to end with tagging, PR merging, and digest verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Publishing a container image release involves many error-prone manual steps: preparing a changelog, creating a release branch, opening and merging a PR, tagging from the default branch, waiting for CI, and verifying the pushed image digest. This Skill orchestrates that entire release flow with strict guardrails so releases always start from a clean, synced default branch. ## Core Features & Use Cases - End-to-end release execution: Runs setup, prep, publish, or complete modes covering changelog prep, release branch creation, PR creation and merge, annotated tag push, workflow wait, and image digest verification. - Guardrailed Git operations: Refuses to prep or publish from feature branches or dirty worktrees, blocks force-pushes and branch-protection bypasses, and stops when human approvals are required. - Reusable setup assets: Generates changelog and release-helper script templates, delegating workflow YAML to the github-workflows skill. - Use Case: A maintainer asks to release version 1.2.0 of a service; the Skill creates release/myservice-v1.2.0, merges the prep PR, tags from the default branch, waits for the image workflow, and reports the verified image digest. ## Quick Start Use the publish-image skill to publish my container image end to end with --mode complete --tag 1.2.0 and report the verified digest.

Frequently Asked Questions about publish-image

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

FAQPage Schema
How do I publish a container image release end to end?

Run the skill with --mode complete --tag X.Y.Z from your project folder. It prepares the changelog on a release branch, creates and merges the PR, tags from the default branch, waits for the image workflow, and verifies the published digest.

How to tag and push a container image release from GitHub?

Use --mode publish from a clean, synced default branch. The helper script creates an annotated tag in the form prefix-vX.Y.Z and pushes it to origin, which triggers the tag-based image workflow.

Why does the release prep fail on my feature branch?

Prep and publish modes require the clean, synced default branch as the release source of truth. Merge your feature branch into the default branch first, switch to it, fast-forward, and rerun the command.

Can I verify a published image tag and digest?

Yes, use --mode verify --tag X.Y.Z --image-name your-registry/repo. The skill runs docker buildx imagetools inspect to confirm the tag exists and records the digest as release evidence.

Does this skill store registry credentials or secrets?

No, it stores only secret and variable names in templates and workflow files. Actual secret values stay in GitHub secrets, the local environment, or the registry login mechanism.