release-packaging

Validate release ZIP archives for required platform entrypoints.

1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/mlinnen/mr-pumpkin --skill release-packaging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-packaging
Source: https://github.com/mlinnen/mr-pumpkin/tree/main/.squad/skills/release-packaging
Command: npx skills add https://github.com/mlinnen/mr-pumpkin --skill release-packaging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mr. Pumpkin's release artifacts must consistently meet a defined deployment contract. This skill validates that each generated ZIP contains all required platform entrypoints and that packaging regressions are caught before release.

Core Features & Use Cases

  • Lifecycle script presence: verifies all four top-level entrypoints (install.sh, install.ps1, update.sh, update.ps1) exist in the versioned folder.
  • Automated integrity checks: provides automated tests that inspect the archive contents and enforce contract conformance.
  • Ephemeral validation: treats release ZIPs as build artifacts and avoids embedding generated binaries in source control by validating them first.
  • Guided packaging coverage: ensures helpers and path expectations are included in packaging tests to prevent missing files.

Quick Start

Run the release packaging validation to verify a generated archive against the deployment contract.

Frequently Asked Questions about release-packaging

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

FAQPage Schema
How do I validate that a release ZIP contains all required entrypoints?

Release packaging validation works by applying automated integrity checks to inspect archive contents and enforce contract conformance. It verifies that required top-level entrypoints exist inside the versioned folder before release.

How do I automate testing for missing lifecycle scripts in GitHub Release assets?

To automate testing for missing lifecycle scripts, apply packaging validation checks to GitHub Release assets across Linux, Windows, and macOS workflows. This verifies the presence of install.sh, install.ps1, update.sh, and update.ps1.

How do I verify cross-platform deployment contracts for macOS, Windows, and Linux archives?

Verify cross-platform deployment contracts by applying deterministic packaging validation across Linux, Windows, and macOS workflows. This enforces that the archive includes the required install.sh, install.ps1, update.sh, and update.ps1 entrypoints.

Can I use automated tests to check real archive contents instead of source control?

Yes, you can test against a real archive to validate contents. This ephemeral validation approach treats release ZIPs as build artifacts, avoiding embedding generated binaries in source control by validating them first.

What is deterministic packaging validation for release artifacts?

Deterministic packaging validation is the process of enforcing consistent deployment contracts for release artifacts. It applies automated checks to generated ZIPs to catch packaging regressions and verify required entrypoints before release.