dogent-release-publish

Automate Dogent release publication with changelog updates, version bumps, and GitHub releases.

4|Updated Nov 14, 2025
One-click install
npx skills add https://github.com/MagicBowen/dogent --skill dogent-release-publish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogent-release-publish
Source: https://github.com/MagicBowen/dogent/tree/main/.agents/skills/dogent-release-publish
Command: npx skills add https://github.com/MagicBowen/dogent --skill dogent-release-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the end-to-end release publication workflow for a Dogent project, coordinating changelog updates, version bumps, artifact builds, and GitHub publishing.

Core Features & Use Cases

  • Update CHANGELOG.md with the accepted user-facing changes according to the repo guidelines.
  • Synchronize version bumps in pyproject.toml and any other versioned locations.
  • Build release artifacts, tag the commit, and publish the GitHub release following the project's packaging workflow.

Quick Start

Provide the target release details and ask this skill to publish the accepted release.

Frequently Asked Questions about dogent-release-publish

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

FAQPage Schema
How do I automate a Python project release with changelog and version updates?

You can automate the end-to-end release publication by updating CHANGELOG.md, bumping versions in pyproject.toml, building artifacts under dist/, and creating GitHub releases automatically. This skill follows the repository's packaging workflow to coordinate the entire release process.

How do I bump a version in pyproject.toml and sync it with a git tag?

To bump a version in pyproject.toml and sync it with a git tag, this skill applies the version bump across versioned locations, builds the release artifacts, tags the commit, and publishes the corresponding GitHub release following your project's dev/package.md workflow.

What is the best way to update CHANGELOG.md before publishing a GitHub release?

The best way to update CHANGELOG.md before publishing a GitHub release is to extract accepted user-facing changes according to your repo guidelines and automatically synchronize them with the version bump and GitHub release creation.

Does this release publishing workflow require any external dependencies?

This release publishing workflow requires no external dependencies. It operates entirely based on your repository's existing dev/package.md workflow guidelines to validate, build, and publish releases.

Can I use this to build artifacts under dist/ and create GitHub releases automatically?

Yes, you can use this to build artifacts under dist/ and create GitHub releases automatically. It coordinates the entire end-to-end workflow including version bumps in pyproject.toml and CHANGELOG.md updates.