skills.rest
israel-salgado
israel-salgadoCOMMUNITY
Explore all skills by this author →
GitHub

dtctl-release

Automate dtctl version bumps, changelog updates, tests, and GitHub releases.

2|1|Updated Apr 15, 2026
Search Tags:#git#changelog#versioning#github#release#ci#dtctl
One-click install
npx skills add https://github.com/israel-salgado/dt-mcp-server --skill dtctl-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dtctl-release
Source: https://github.com/israel-salgado/dt-mcp-server/tree/main/.agents/skills/dtctl-release
Command: npx skills add https://github.com/israel-salgado/dt-mcp-server --skill dtctl-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end dtctl release workflow, ensuring version bumps, changelog updates, test execution, commit/tag/push, and GitHub release notes are performed consistently.

Core Features & Use Cases

  • End-to-end release orchestration — coordinates bumping the version, updating CHANGELOG.md, running tests, committing changes, creating Git tags, and publishing GitHub release notes.
  • Quality guardrails — enforces a clean working tree, main-branch alignment, and up-to-date remote status to avoid partial or conflicting releases.
  • Release documentation — generates and attaches release notes, with steps aligned to semantic versioning and GoReleaser workflow.

Quick Start

Initiate the release workflow by prompting the AI to run the release process for a new dtctl version.

Frequently Asked Questions about dtctl-release

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

FAQPage Schema
How do I automate a GitHub release workflow with changelog generation and version bumps?▼

Automating a GitHub release workflow involves coordinating semantic version bumps, CHANGELOG.md updates, test execution, and Git tag creation. This ensures consistent release documentation and packaging directly from the main branch.

What is the best way to enforce a clean working tree before creating a Git tag for a release?▼

Enforcing a clean working tree before creating a Git tag requires checking for uncommitted changes and verifying main-branch alignment. This prevents partial or conflicting releases and ensures remote status is up-to-date.

How does semantic versioning work with changelog updates in a CI release process?▼

Semantic versioning in a CI release process dictates the version bump based on changes, while changelog updates document these changes. The workflow runs tests, commits the version bump, and pushes the tag to publish release notes.

Do I need to align with the main branch before publishing GitHub release notes?▼

Yes, you need to align with the main branch before publishing GitHub release notes. The release workflow enforces main-branch alignment and up-to-date remote status to avoid partial releases and ensure a clean working tree.

Why does my automated release workflow fail when there are uncommitted changes?▼

An automated release workflow fails on uncommitted changes because it enforces a clean working tree as a quality guardrail. This prevents conflicting states during version bumps, changelog updates, and Git tag creation.

Related Skills

Explore More Software Engineering Skills→
MCrankMCrank

create-release

Automate CodeCompress releases with Gitflow, Semantic Versioning, and changelog generation.

Community
Advanced
leodinhsaleodinhsa
1

deploy-skillops

Automate SkillOps releases with version bumps, tagging, and publishing.

Community
Advanced
bmad-code-orgbmad-code-org
8

bmad-os-changelog

Generate structured changelog entries from git history and pull request metadata.

Official
Intermediate
rfxlamiarfxlamia
100

releasing

Automate version bumping, changelog generation, git tagging, and GitHub releases.

Community
Advanced