ash-library-hotfix

Automate emergency hotfix branches for the ash_cookie_consent library.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, rapid response process for critical bugs, security vulnerabilities, or data loss issues in the ash_cookie_consent library. It ensures immediate fixes are deployed with minimal disruption, protecting your application and users.

Core Features & Use Cases

  • Emergency Patching: Quickly create hotfix branches, apply minimal fixes, and bump patch versions.
  • Thorough Testing: Guides through essential testing to ensure the fix works without introducing new issues.
  • Rapid Deployment: Automates Hex.pm publishing and GitHub release creation for swift distribution.
  • Use Case: When a critical security vulnerability is reported in ash_cookie_consent, use this skill to guide you through creating, testing, and releasing a hotfix within hours, ensuring your application remains secure and compliant.

Quick Start

Create a hotfix for ash_cookie_consent version 0.1.0 to patch a critical security vulnerability.

Frequently Asked Questions about ash-library-hotfix

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

FAQPage Schema
How do I create and release a hotfix for a critical bug in an Elixir library?

A hotfix is an emergency patch released outside your normal cycle for critical bugs, security vulnerabilities, or data loss. This Skill automates the process: create a hotfix branch, apply minimal fixes, add regression tests, bump the patch version, run full tests, and publish to Hex.pm within hours.

What steps should I follow to patch a security vulnerability in ash_cookie_consent?

Confirm the issue is critical, create a hotfix branch, apply only the necessary fix, add regression tests, update the CHANGELOG, bump the patch version, run targeted and full tests, commit and tag, merge to main, publish to Hex.pm, and issue release notes and user communications.

Can I automate publishing a hotfix release to Hex.pm?

Yes. This Skill guides you through the complete automated workflow: it enforces minimal fixes, ensures regression tests pass, manages version bumping, and automates publishing to Hex.pm alongside GitHub release creation for rapid distribution.

When should I use a hotfix branch instead of a regular release?

Use a hotfix for production-impact incidents: security vulnerabilities, data loss, crashes, or other critical defects that require immediate deployment. Hotfixes enforce minimal changes and rapid testing to minimize risk while maintaining emergency response speed.

What testing is required before releasing a hotfix to production?

Run both targeted tests specific to the bug fix and the full test suite to ensure the fix resolves the issue without introducing regressions. This Skill enforces both testing levels before allowing publication to Hex.pm.