NO-JIRA: Add check-release-readiness Claude Code skill

[suleymanakbas91]

Summary

Add a new Claude Code skill (/lvms:check-release-readiness) that performs comprehensive release readiness checks for LVMS.

The skill verifies:

• Release branches exist on lvm-operator and topolvm repos
• Go version matches Kubernetes requirements
• k8s.io/* dependencies are at correct versions
• CSI dependencies use matching Kubernetes versions (with recommendations)
• TopoLVM replacement points to openshift/topolvm
• Upstream TopoLVM fork sync status (staleness detection with thresholds)
• Controller-runtime version compatibility
• Makefile tool versions (ENVTEST_K8S_VERSION, OPERATOR_SDK_VERSION)
• rpms.lock.yaml existence

Usage:

# Check upstream main branch (default)
/lvms:check-release-readiness --version 4.21 --k8s 1.34

# Check a specific upstream branch
/lvms:check-release-readiness --version 4.21 --k8s 1.34 --branch release-4.21

# Check local working directory
/lvms:check-release-readiness --version 4.21 --k8s 1.34 --local

The skill checks the upstream repository by default to ensure accurate release readiness assessment.

Test plan

• Run /lvms:check-release-readiness --version 4.21 --k8s 1.34 and verify report is generated
• Verify all checks produce expected results
• Verify CSI dependency recommendations are accurate

🤖 Generated with Claude Code

[openshift-ci-robot]

@suleymanakbas91: This pull request explicitly references no jira issue.

Details

In response to this:

Summary

Add a new Claude Code skill (/lvms:check-release-readiness) that performs comprehensive release readiness checks for LVMS.

The skill verifies:

• Release branches exist on lvm-operator and topolvm repos
• Go version matches Kubernetes requirements
• k8s.io/* dependencies are at correct versions
• CSI dependencies use matching Kubernetes versions (with recommendations)
• TopoLVM replacement points to openshift/topolvm
• Upstream TopoLVM fork sync status (staleness detection with thresholds)
• Controller-runtime version compatibility
• Makefile tool versions (ENVTEST_K8S_VERSION, OPERATOR_SDK_VERSION)
• rpms.lock.yaml existence

Usage:

# Check upstream main branch (default)
/lvms:check-release-readiness --version 4.21 --k8s 1.34

# Check a specific upstream branch
/lvms:check-release-readiness --version 4.21 --k8s 1.34 --branch release-4.21

# Check local working directory
/lvms:check-release-readiness --version 4.21 --k8s 1.34 --local

The skill checks the upstream repository by default to ensure accurate release readiness assessment.

Test plan

• Run /lvms:check-release-readiness --version 4.21 --k8s 1.34 and verify report is generated
• Verify all checks produce expected results
• Verify CSI dependency recommendations are accurate

🤖 Generated with Claude Code

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: suleymanakbas91

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [suleymanakbas91]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jeff-roche]

/lgtm

[openshift-ci]

@suleymanakbas91: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.