publish

Automate a deterministic release workflow for publishing code-kg to PyPI with Poetry.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/Flux-Frontiers/doc_kg --skill publish-flux-frontiers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish
Source: https://github.com/Flux-Frontiers/doc_kg/tree/main/.claude/skills/publish
Command: npx skills add https://github.com/Flux-Frontiers/doc_kg --skill publish-flux-frontiers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a clear, repeatable release process so you can publish code-kg to PyPI safely and consistently without missing critical steps like version bumps, changelog updates, tagging, and builds.

Core Features & Use Cases

  • Version bump + CHANGELOG coordination: Aligns the semantic version, changelog entries, and repository metadata so release notes match the released artifact.
  • Commit/tag/build/publish pipeline: Drives an end-to-end workflow from a clean repo through building the distribution and publishing to PyPI (or TestPyPI).
  • Post-release housekeeping: Guides follow-up steps like pushing tags and saving a snapshot for traceability.

Quick Start

Use the publish skill to cut a new code-kg release by bumping the version, updating CHANGELOG.md, committing with the skip-snapshot flag, tagging, building, publishing to PyPI, and pushing tags to GitHub.

Frequently Asked Questions about publish

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

FAQPage Schema
How do I publish a Python package to PyPI using Poetry?

To publish a Python package to PyPI using Poetry, you need a clean git working tree, passing tests, and a configured PyPI token to execute stepwise versioning, build, and publish commands.

How do I coordinate semantic version bumps with CHANGELOG.md updates for a release?

Coordinating semantic version bumps with CHANGELOG.md updates aligns your repository metadata and changelog entries so release notes match the built distribution artifact. This automated workflow ensures consistency during the release cycle.

What do I need to set up before cutting a new release with Poetry?

Before cutting a new release with Poetry, you need a clean git working tree, passing pre-commit checks, a configured PyPI token, and a passing test suite to ensure deterministic and safe package publishing.

Does publishing to TestPyPI work with this automated release pipeline?

Publishing to TestPyPI works within this release pipeline as an alternative target to PyPI. The workflow drives the end-to-end process from building the distribution to publishing to either package index.

Why does my release workflow require a clean git working tree?

Your release workflow requires a clean git working tree to guarantee deterministic versioning, tagging, and builds. Uncommitted changes risk shipping untracked code or corrupting the semantic version and commit tag coordination.

What is the best way to tag commits and push tags after a PyPI release?

The best way to tag commits and push tags after a PyPI release is through post-release housekeeping, which guides pushing tags to GitHub and saving a snapshot for traceability once the package is published.