skills.rest
agoodway
agoodwayOFFICIAL
Explore all skills by this author →
GitHub

publish

Validate project readiness and confirm version before running the just publish workflow.

1|Updated May 7, 2026
Search Tags:#versioning#publishing#release#ci-cd#tagging#just#github release
One-click install
npx skills add https://github.com/agoodway/GoodSkills --skill publish-agoodway
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: publish
Source: https://github.com/agoodway/GoodSkills/tree/main/skills/publish
Command: npx skills add https://github.com/agoodway/GoodSkills --skill publish-agoodway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publishing a release usually requires coordinating version discovery, tests and builds, tagging, pushing, and GitHub release creation without forgetting required checks or prerequisites.

Core Features & Use Cases

  • Release readiness validation: Confirms a justfile exists and that it contains a publish recipe before attempting any release actions.
  • Version discovery and confirmation: Detects the current version and asks the user to confirm before running the publish workflow to reduce accidental releases.
  • Failure visibility and common troubleshooting: Surfaces full command output when publishing fails and highlights typical blockers such as missing gh, authentication issues, or a dirty working tree.

Quick Start

Ask to run the publish skill for your project by saying: /publish

Frequently Asked Questions about publish

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

FAQPage Schema
How do I automate GitHub release publishing with a justfile?▼

GitHub release publishing is automated by validating a root justfile with a publish recipe, discovering the current version, and running the release command after explicit user confirmation.

What prerequisites do I need to run a just publish workflow for versioned releases?▼

The just publish workflow requires a root justfile containing a publish recipe. Common blockers include missing gh CLI authentication or a dirty working tree.

Can I use this to tag and publish a release without manually checking the current version?▼

Yes, version discovery is automated by checking common manifest files for the current version, but explicit user confirmation is required before executing the publish pipeline.

Why does my just publish release pipeline fail during GitHub release creation?▼

Release pipeline failures are surfaced with full command output. Typical blockers include missing gh CLI, authentication issues, or a dirty git working tree.

What is the safest way to run CI-CD versioning and tagging before a GitHub release?▼

Safe release publishing validates project readiness by confirming the justfile exists and contains a publish recipe before attempting any version tagging or release actions.

Related Skills

Explore More Product & Management Skills→
GenEducationGenEducation

bmad-os-release-module

Coordinate software releases with version bumps, changelog updates, git tagging, npm publishing, and GitHub release creation.

Official
Intermediate
codewithmukeshcodewithmukesh
640

ci-cd

Automate .NET build, test, and deployment pipelines with GitHub Actions or Azure DevOps.

Official
Intermediate
masx200masx200
2

github-release

Create GitHub releases from tagged commits using gh CLI.

Community
Advanced
nklischnklisch
7

release

Draft changelog entries from commits and execute the project's release process.

Community
Advanced