ash-library-release

Coordinate ash_cookie_consent releases from versioning to Hex.pm publishing.

2|Updated Nov 1, 2025
One-click install
npx skills add https://github.com/shotleybuilder/ash_cookie_consent --skill ash-library-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ash-library-release
Source: https://github.com/shotleybuilder/ash_cookie_consent/tree/main/.claude/skills/ash-library-release
Command: npx skills add https://github.com/shotleybuilder/ash_cookie_consent --skill ash-library-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the entire release process for the ash_cookie_consent Elixir library, from version bumping and CHANGELOG updates to quality checks, Hex.pm publishing, and GitHub release creation. It eliminates manual errors and ensures consistent, professional releases, freeing up developer time.

Core Features & Use Cases

  • Automated Versioning: Guides through semantic versioning, updating CHANGELOG.md, and bumping mix.exs.
  • Quality Assurance: Enforces running comprehensive tests, formatting checks, Credo, and Dialyzer before release.
  • Seamless Publishing: Handles building the Hex.pm package, creating Git tags, and publishing to Hex.pm and GitHub.
  • Use Case: After developing new features for ash_cookie_consent, use this skill to ensure a smooth, error-free release of version 0.2.0, complete with updated documentation and release notes, without missing any critical steps.

Quick Start

Release ash_cookie_consent version 0.2.0 with new features and bug fixes.

Frequently Asked Questions about ash-library-release

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

FAQPage Schema
How do I automate releasing an Elixir library to Hex.pm?

Automate Hex.pm releases by coordinating your full release workflow—version bumping, CHANGELOG updates, quality checks, package building, Git tagging, and publishing—in one streamlined process. This eliminates manual steps and ensures consistent, professional releases.

What steps are involved in a semantic versioning release for an Ash Framework library?

Semantic versioning releases require updating mix.exs, migrating CHANGELOG entries, running tests and formatting checks, building the package, committing changes, creating Git tags, publishing to Hex.pm, and generating a GitHub release. Automating these steps prevents errors and maintains consistency.

Can I enforce quality checks before publishing to Hex.pm?

Yes. Pre-release quality assurance runs comprehensive tests, formatting validation, Credo linting, and Dialyzer type checking before your package builds and publishes. This catches issues early and ensures only production-ready code reaches Hex.pm.

Do I need to manually create Git tags and GitHub releases when publishing?

No. The release workflow automatically creates Git tags, publishes to Hex.pm, and generates GitHub releases as part of the coordinated process. This removes manual overhead and keeps version control synchronized with package publishing.

What happens if a pre-release validation fails?

Pre-release checks halt the workflow if tests fail, formatting is incorrect, or type checking reveals issues. This prevents incomplete or broken packages from reaching Hex.pm and gives you a chance to fix problems before proceeding.