Release Readiness Checker

Pre-release checklist for shipping software — verify tests pass, changelog updated, version bumped, no debug code, dependencies clean, docs current, no secre...

This skill generally does what its name says, but there are important mismatches and practical risks to consider before installing or running it: - Tooling mismatch: SKILL.md expects git, python3, ripgrep (rg), npm (and npm audit), and the GitHub CLI (gh), among others. The registry metadata lists no required binaries — verify these tools are available in the environment where you plan to run the skill. - Credentials and network access: The skill will call networked CLIs (npm audit, gh) that use existing credentials or tokens. The skill metadata declares no required env vars, so ensure you do not expose high-privilege tokens when running this — prefer least-privilege accounts or run in a read-only CI context. - Secret-handling: The checker searches the repo for secret-looking patterns. Review how outputs are displayed or transmitted; do not run this skill in a context where its output could be forwarded outside a trusted environment, and consider running it on a local fork or in a sandbox. - Missing explicit requirements: Ask the skill author (or your registry maintainer) to update metadata to list required binaries and any optional credentials, and to document what network calls the checks perform and where outputs go. If you cannot get that, run the commands manually in a controlled environment instead of invoking the skill autonomously. - Operational advice: Run the checks from a CI job or a developer workstation with only the minimal necessary credentials, and inspect the full SKILL.md (including truncated parts) for any additional network endpoints or commands before use.

Type: OpenClaw Skill Name: release-readiness-checker Version: 1.0.0 The release-readiness-checker skill is a comprehensive auditing tool designed to verify project health before a software release. It uses standard command-line utilities like git, ripgrep (rg), and the GitHub CLI (gh) to check for version bumps, changelog updates, debug code, committed secrets, and CI status. The logic is transparent, well-documented in SKILL.md, and strictly adheres to its stated purpose without any signs of data exfiltration, obfuscation, or malicious intent.