← ClaudeAtlas

release-validatelisted

Validates package release readiness across version consistency, cross-platform link integrity, npm package content, setup script smoke testing, skill fixture suite runs (Phase 4), shell portability static checks (Phase 5), cross-repo-style fixture coverage (Phase 6, shipped in v1.15.0), cross-AI-tool registration parity (Phase 7, shipped in v1.15.0), and release artifact generation (Phase 8). Use before running `pnpm release` to catch issues that structure tests may miss. Top-level orchestrator at `scripts/release_check.sh` runs every phase and is wired into `.github/workflows/release.yml` as a pre-publish gate. Produces `docs/reports/release-validate/<version>/RELEASE-CHECK.md` suitable verbatim for the GitHub Release body.
qwedsazxc78/devops-ai-skill · ★ 2 · DevOps & Infrastructure · score 68
Install: claude install-skill qwedsazxc78/devops-ai-skill
# Release Validation Skill ## Purpose Pre-release quality gate that validates the devops-ai-skill pack is ready to publish. Covers four areas that existing structure tests (`test-structure.sh`) do not fully address: 1. **Package release checks** — version sync, changelog, npm pack content, git state, badge accuracy 2. **Cross-platform link validation** — all 4 platforms correctly reference skills, prompts, and agents 3. **Skill & pipeline parity** — every skill/pipeline on disk is registered on every platform 4. **Setup script smoke testing** — dry-run validation of setup scripts in a sandboxed temp directory This skill is the only one that validates the skill pack itself (meta-validation). It bridges the gap between `test-structure.sh` (static file checks) and `release.sh` (publish). Think of it as a pre-flight checklist that catches semantic issues — dead cross-references, missing registrations, npm packaging gaps, or setup script regressions — that static checks cannot detect. ## Activation This skill activates when the user: - Asks to validate a release before publishing - Runs a pre-release check or readiness assessment - Wants to verify cross-platform consistency after adding a skill or pipeline - Asks to smoke-test the setup scripts - Asks to check if the pack is ready for `pnpm release` ## Step 0: Discover Repository Layout **Do NOT assume hardcoded counts or file lists.** Discover the pack structure at runtime. ### 0a: Discover All Skills Build the canonica