qcc-release

Automate qcc_plus version releases with Git, GoReleaser, and GitHub.

42|12|Updated Nov 23, 2025
One-click install
npx skills add https://github.com/yxhpy/qcc_plus --skill qcc-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qcc-release
Source: https://github.com/yxhpy/qcc_plus/tree/main/.claude/skills/qcc-release
Command: npx skills add https://github.com/yxhpy/qcc_plus --skill qcc-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, goreleaser, docker, github-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of version release, GoReleaser automation, and publishing workflows in the qcc_plus project, streamlining the deployment and distribution process.

Core Features & Use Cases

  • Version Release Automation: Automates the tagging, building, and releasing of software versions.
  • GoReleaser Integration: Utilizes GoReleaser for building and publishing Go applications.
  • Docker Image Management: Handles the creation and distribution of Docker images.
  • Change Log Generation: Automatically generates CHANGELOG entries for new releases.
  • GitHub Release Creation: Creates GitHub releases with built artifacts.
  • Use Case: For a developer working on the qcc_plus project, this Skill can automate the process of releasing a new version of the project, including building the application, creating a Docker image, and publishing it to GitHub.

Quick Start

Use the qcc-release skill to tag and release a new version of the qcc_plus project with the tag 'v1.2.0'.

Frequently Asked Questions about qcc-release

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

FAQPage Schema
How do I automate Go application version releases with GoReleaser and Docker?

Automate Go application version releases by using GoReleaser to handle version tagging, build application binaries, create Docker images, and generate GitHub releases. This streamlines the entire deployment and distribution process.

What do I need to set up before automating GitHub release workflows?

Before automating GitHub release workflows, you need Git, GoReleaser, Docker, and the GitHub CLI installed and configured. You also need GitHub API access to create releases and push artifacts directly from your environment.

Can I automatically generate a CHANGELOG and Docker image for a new GitHub release?

Yes, you can automatically generate a CHANGELOG and create a Docker image for a new GitHub release. The automation workflow handles changelog generation, builds the application binaries, packages the Docker image, and publishes everything to GitHub.

How does GoReleaser integrate with Docker for building and publishing application binaries?

GoReleaser integrates with Docker by compiling application binaries and packaging them into Docker images during the release process. It then publishes these images alongside the compiled binaries to a GitHub release, ensuring consistent distribution.

What is the best way to tag and release a new software version using Git and GitHub CLI?

The best way to tag and release a new software version is to automate the process using Git, GoReleaser, and the GitHub CLI. This combination manages version tagging, builds binaries, creates Docker images, and formalizes the GitHub release.