test-apps-published-package-validation

Validate published packages across npm, PyPI, RubyGems, Maven Central, Docker Hub, and Homebrew.

836|66|Updated Feb 3, 2025
One-click install
npx skills add https://github.com/kreuzberg-dev/html-to-markdown --skill test-apps-published-package-validation-kreuzberg-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-apps-published-package-validation
Source: https://github.com/kreuzberg-dev/html-to-markdown/tree/main/.codex/skills/test-apps-published-package-validation
Command: npx skills add https://github.com/kreuzberg-dev/html-to-markdown --skill test-apps-published-package-validation-kreuzberg-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that released software packages function correctly across various platforms and languages after they have been published to public repositories.

Core Features & Use Cases

  • Cross-Platform Validation: Tests packages published on npm, PyPI, RubyGems, Maven Central, Docker Hub, and Homebrew.
  • Automated Version Syncing: Keeps test app manifests aligned with the main project's version.
  • Use Case: After releasing a new version of a library, this Skill can automatically verify that the published package installs and runs as expected in Node.js, Python, and Ruby environments.

Quick Start

Run the test suite for the published Node.js package from the repository root.

Frequently Asked Questions about test-apps-published-package-validation

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

FAQPage Schema
How do I validate a published npm package after release?

Validate published npm packages by automating installation and testing of released versions. This Skill verifies that your published Node.js package functions correctly in target environments after deployment to public repositories.

Can I test published packages across multiple ecosystems like PyPI and RubyGems?

Yes, cross-platform package validation supports npm, PyPI, RubyGems, Maven Central, Docker Hub, and Homebrew. It automates installation and testing across these ecosystems to ensure released versions maintain integrity and functionality.

How do I keep test app manifests synced with my main project's release version?

Automated version syncing keeps test app manifests aligned with the main project's version. It supports updating pyproject.toml, package.json, Gemfile, go.mod, pom.xml, .csproj, and Cargo.toml files automatically.

Does package validation work with Docker Hub and Homebrew releases?

Yes, package validation works with Docker Hub and Homebrew releases. It automates the installation and testing of released versions from these repositories to ensure integrity and functionality across your deployment pipeline.

What is the best way to verify package integrity across Node.js, Python, and Ruby environments?

The best way to verify package integrity is automating installation and testing of released versions across multiple environments. This Skill validates that published packages install and run as expected in Node.js, Python, and Ruby.

Why should I validate published packages instead of just running CI tests before release?

Validating published packages ensures the released version functions correctly after publication to public repositories, catching registry or packaging issues that pre-release CI tests cannot detect, guaranteeing integrity across target platforms.