skills.rest
haojing8312
haojing8312COMMUNITY
Explore all skills by this author →
GitHub

workclaw-release-readiness

Validate WorkClaw release-sensitive changes and generate a GREEN/YELLOW/RED verdict.

154|1|Updated Feb 20, 2026
Search Tags:#versioning#verification#release#shipping#readiness#workclaw
One-click install
npx skills add https://github.com/haojing8312/WorkClaw --skill workclaw-release-readiness
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workclaw-release-readiness
Source: https://github.com/haojing8312/WorkClaw/tree/main/.agents/skills/workclaw-release-readiness
Command: npx skills add https://github.com/haojing8312/WorkClaw --skill workclaw-release-readiness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that any changes affecting versioning, installer branding, release documentation, packaging, or vendor lanes are thoroughly validated before a WorkClaw branch is deemed ready for shipment, preventing accidental releases with broken artifacts.

Core Features & Use Cases

  • Targeted Release Checks: Executes specific pnpm commands based on the changed release surface (e.g., version check, installer validation, documentation review).
  • Verdict Generation: Produces a clear GREEN/YELLOW/RED recommendation with evidence, blocking issues, and required follow‑ups.
  • Decision Support: Guides product managers and engineers in confirming ship readiness after release‑sensitive work.

Quick Start

Ask the skill to evaluate the current branch for release readiness and receive a verdict with required actions.

Frequently Asked Questions about workclaw-release-readiness

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

FAQPage Schema
How do I check release readiness before shipping a software branch?▼

Release readiness checks validate version, installer, documentation, packaging, and vendor lane changes. The skill evaluates modified release-sensitive files to determine shipping suitability and generates a GREEN, YELLOW, or RED verdict.

What does a GREEN, YELLOW, or RED release verdict mean for my branch?▼

A GREEN, YELLOW, or RED verdict indicates shipping suitability based on release validation. GREEN means safe to ship, YELLOW requires follow-ups, and RED lists blocking issues preventing release.

How do I validate versioning and installer packaging changes before a release?▼

Validate versioning and installer packaging by executing targeted pnpm commands based on the changed release surface. This skill runs specific checks for version, installer branding, and documentation to ensure artifacts are not broken.

Can I use this release validation for branches with vendor lane modifications?▼

Yes, release validation applies to branches where release-sensitive files, including vendor lane changes, are modified. It assesses these specific modifications to determine if the branch is ready for shipment.

What should I do if my release readiness check returns blocking issues?▼

If release readiness checks return blocking issues, the generated RED verdict provides a list of these issues and recommends required next steps. You must resolve these follow-ups before proceeding with shipment.

Related Skills

Explore More Product & Management Skills→
Xpotato1024Xpotato1024
1

devkit-release-maintainer

Validate devkit release metadata across tags, installers, and version outputs.

Community
Advanced
Omar-ObandoOmar-Obando
44

deployment

Design CI/CD pipelines, Docker configurations, and SemVer release workflows.

Community
Intermediate
einja-inceinja-inc
1

cli-release

Automate @einja/cli package builds, tests, versioning, tagging, changelog notes, and GitHub publishing with enforced checks using pnpm, npm, and gh tools.

Official
Intermediate
d-o-hubd-o-hub
11

github-workflows-release-management

Diagnose, fix, and optimize GitHub Actions workflows for Rust CI/CD pipelines.

Community
Advanced