release

Automate Docker-based release workflows with release-please version management.

Updated Feb 5, 2026

Search Tags:#automation #ci/cd #versioning #deployment #release #docker

Ready to run

npx skills add https://github.com/sho7650/tech-news-curator --skill release-sho7650

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/sho7650/tech-news-curator/tree/main/.claude/skills/release
Command: npx skills add https://github.com/sho7650/tech-news-curator --skill release-sho7650

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the complex and error-prone process of releasing new versions of software components, ensuring consistency and reducing manual effort.

Core Features & Use Cases

Automated Versioning: Integrates with release-please to manage semantic versioning based on conventional commits.
CI/CD Integration: Orchestrates build, test, and push steps for Docker images.
Pre-Release Validation: Enforces a checklist of tests, linting, and checks before deployment.
Use Case: When you need to deploy a new version of the API and frontend, this skill will ensure all tests pass, build the Docker images, and prepare them for pushing to the registry.

Quick Start

Use the release skill to perform a patch version bump for the api component.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate semantic versioning for Docker-based deployments?▼

Automate semantic versioning for Docker-based deployments by integrating release-please to read conventional commits and orchestrate build, test, and push operations. This ensures consistent version bumps across your API and frontend services.

What checks are required before pushing a Docker image to a registry?▼

Before pushing a Docker image, you must enforce a checklist of tests, linting, and checks. The workflow ensures a clean working tree and passes E2E tests before image deployment to the registry.

Does this release workflow support both API and frontend services?▼

Yes, the release workflow supports both API and frontend services. It orchestrates Docker build, test, linting, and push operations specifically for these components to prepare them for registry deployment.

How do I use conventional commits to trigger a patch version bump?▼

Trigger a patch version bump by using conventional commits in your repository. The workflow integrates release-please to automatically manage semantic versioning based on your commit history and prepare the release.

What happens if my working tree is not clean during the release process?▼

During the release process, if your working tree is not clean, the workflow will halt. It enforces a clean working tree and requires all E2E tests to pass before proceeding to Docker image deployment.