check-release

Verify TorchJD releases via docs, PyPI installation, and API smoke tests.

392|21|Updated Jun 1, 2024
One-click install
npx skills add https://github.com/SimplexLab/TorchJD --skill check-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-release
Source: https://github.com/SimplexLab/TorchJD/tree/main/skills/check-release
Command: npx skills add https://github.com/SimplexLab/TorchJD --skill check-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill checks whether a newly published TorchJD release is actually live, correctly documented, and installable, reducing the risk of shipping a broken release.

Core Features & Use Cases

  • Docs Validation: Confirms the release appears in the TorchJD documentation version switcher and that stable points to the new release.
  • Package Verification: Installs TorchJD from PyPI in an isolated environment and checks that the published version matches the expected release.
  • Smoke Testing: Imports and runs newly added public classes or functions to catch packaging or runtime regressions immediately after release.
  • Use Case: After merging a release, use this Skill to confirm the docs, PyPI package, and new APIs all work end to end before announcing the release.

Quick Start

Use the check-release skill to verify the TorchJD release version 0.16.0.

Frequently Asked Questions about check-release

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

FAQPage Schema
How do I verify a TorchJD release is correctly published on PyPI?

To verify a TorchJD release on PyPI, install the package in an isolated environment and confirm the installed version matches the expected release metadata to ensure packaging integrity.

What is the best way to check TorchJD documentation availability after a release?

Checking TorchJD documentation availability involves confirming the new release appears in the documentation version switcher and that the stable pointer directs to the newly published version.

How do I run smoke tests on newly added public classes in a TorchJD release?

Running smoke tests for a TorchJD release requires importing and executing newly added public classes or functions to catch packaging or runtime regressions immediately after publication.

When should I perform release verification for TorchJD projects?

Release verification for TorchJD should be performed immediately after merging a release to confirm documentation, PyPI installation, and new APIs work end to end before announcing the release.

Does TorchJD release verification require reading project metadata and changelog details?

Yes, TorchJD release verification requires reading project metadata and changelog details to confirm expected versioned documentation and validate installed package behavior accurately.

Why does the installed TorchJD package version not match the expected release?

If the installed TorchJD package version does not match the expected release, PyPI publication may be broken or delayed, requiring isolated environment re-installation and metadata verification.