pr-review-rw

Reviews pull requests touching on-prem Kubernetes clusters with independent live-cluster verification.

Updated Apr 16, 2025
One-click install
npx skills add https://github.com/damoke012/eks_code --skill pr-review-rw-damoke012
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review-rw
Source: https://github.com/damoke012/eks_code/tree/main/.claude/skills/pr-review-rw
Command: npx skills add https://github.com/damoke012/eks_code --skill pr-review-rw-damoke012

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Reviewing PRs that change on-prem cluster state is risky when reviewers trust the author's claims; this Skill enforces independent verification against the live cluster and source repo before approving changes to RisingWave namespaces or platform-wide resources. ## Core Features & Use Cases - Structured 8-phase review workflow: reads the PR diff, identifies the target namespace from source manifests, verifies every claim against the live cluster with kubectl, and drafts a Round-N comment in BLOCKER/CLEARED/ADVISORY format. - Namespace coordination gate: applies the Tim-coordination rule for the risingwave namespace on op-usxpress-dev and scopes ownership claims per cluster. - Quality-bar checklist: catches real incident patterns such as readiness probes on wrong ports, deleted comments containing counter-arguments, and server-side-apply conflicts on live objects. - Use Case: A teammate opens a PR patching a HelmRelease in the platform repo; you run /pr-review-rw iaac-talos-flux-platform 42 to verify the live release version, confirm the target namespace, and post an evidence-backed Round-1 review comment. ## Quick Start Ask the assistant to review PR number 7 on the iaac-talos-flux-cluster repository using the pr-review-rw workflow.

Frequently Asked Questions about pr-review-rw

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

FAQPage Schema
How do I review a PR that changes Kubernetes cluster state?▼

Use the structured workflow: fetch the PR with gh pr view and gh pr diff, identify the target namespace from the source repo manifests, then verify every claim against the live cluster with kubectl before drafting a findings table and Round-N comment.

How to verify PR claims against a live Kubernetes cluster?▼

Run a standard verification battery with kubectl: check pod status in the target namespace, compare live resource fields against patched values with jsonpath, and inspect recent events for pre-applied changes. Never rely on the PR author's description alone.

When is Tim coordination required for RisingWave namespace changes?▼

Coordination is required on the op-usxpress-dev cluster when a PR targets the risingwave namespace or makes cluster-wide platform changes with possible RisingWave impact. The risingwave-2 namespace is dev-only and needs no coordination gate.

Can this review workflow run inside a GitHub Codespace?▼

No, the Codespace cannot reach the on-prem cluster. All live-cluster verification commands using kubectl and aws must run on WSL, while GitHub operations via the gh CLI work from either environment.

What common mistakes does this PR review checklist catch?▼

It catches readiness probes targeting sidecar ports instead of traffic ports, deleted comments containing arguments against the change, server-side-apply conflicts on live objects, and Service targetPorts that no container actually binds.