rithwik-01
- 9 skills
- 0 followers
- 6 hours ago last updated
- ▌ K8S Fix · rithwik-01Implement an approved Kubernetes fix - plan loop with an adversarial plan reviewer, red-first test then minimal change on a new branch, six parallel read-only reviewers, synthesis, and an evidence-based verifier gate, both loops bounded at three rounds. Use only after /k8s-triage returned REAL and the user explicitly approved proceeding. Never commits, never pushes, never posts.
- ▌ K8S Setup · rithwik-01First-run setup for the k8s-contributor plugin - discover your kubernetes clones, check prerequisites, cache a build profile per repo, resolve the contributor docs, and offer to install the recommended permission deny rules. Use once after installing the plugin, or any time your workspace or tooling changed. Safe to re-run.
- ▌ K8S Report · rithwik-01Turn a completed Kubernetes run's raw evidence into the human-facing deliverables - a one-page report, a PR description filled from the repo's actual template, an optional issue comment, and an unexecuted commit plan. Use to package results, draft a PR body or issue comment, or summarize what was proven. Produces drafts only and never posts or commits anything.
- ▌ K8S Triage · rithwik-01Triage a Kubernetes GitHub issue end to end - fetch it, resolve the local clone, detect the repo profile, fan out five parallel read-only investigators (classification, duplicates, code location, is-it-really-a-bug, reproduction), then synthesize one verdict and stop for approval. Use for any kubernetes or kubernetes-sigs issue URL that needs triaging, investigating, or reproducing.
- ▌ K8S Verify · rithwik-01Run the applicable verification gates for a Kubernetes change and decide pass or fail from artifacts on disk - build, static and generated-code checks, the red-to-green regression proof, unit plus race, diff hygiene, integration, cluster, flake statistics, and the CI-parity checklist. Use to verify a fix, re-run gates, or check whether work is actually proven.
- ▌ K8S Profile · rithwik-01Detect and cache the build/test/verify profile for a Kubernetes-ecosystem repo clone - real Makefile targets, test tiers, etcd and kind requirements, assertion library, OWNERS, SIG, PR template, generated-code refresh command, and per-gate runtime estimates. Use before running any gate against a repo, or when build commands are unknown or look wrong.
- ▌ K8S Codebase Patterns · rithwik-01How to write a change that looks native to the Kubernetes package it lands in - find the nearest analogous code and imitate it, use the helpers the package already imports, never add a dependency, and never invent a new pattern. Load before writing or reviewing any Go code in a kubernetes or kubernetes-sigs repo.
- ▌ K8S Contrib Guidelines · rithwik-01 bundleKubernetes contributor process read from the kubernetes/community docs on disk (a local clone if you have one, otherwise a fetched-and-cached copy) - issue triage verdicts and Prow commands, PR conventions and release notes, coding and testing conventions, API change rules, logging and metrics conventions, OWNERS, and cherry-pick eligibility. Load before triaging an issue, writing a plan, reviewing a diff, or drafting a PR description.
- ▌ K8S Verification Matrix · rithwik-01 bundleThe pass criteria for any Kubernetes-ecosystem change - the G0-G10 gate definitions, which gates are mandatory for which change class, the red-to-green regression proof, flake statistics, and the gate.json schema. Load before deciding whether work is verified, before running verification, and before reporting PASS or FAIL.