openshift / oc

What's here is generic engineering-workflow tooling the oc maintainers checked in for their own use: an Effective Go skill that points at golang.org's own idiom guide, and two session-memory skills — learn-session and learn-history — that read past Claude Code sessions on this project and pull out what is worth writing into AGENTS.md or longer-term memory. All three are dep_class ready: nothing to install, connect, or pay for beyond the skill text itself.

This is for a contributor to the oc codebase who wants their coding agent to write idiomatic Go and to keep learning across sessions on this specific repository — not for someone who wants an agent that already knows how to run oc against a live cluster. oc's own README describes a large Kubernetes/OpenShift client with a real build chain (GSSAPI, kubectl, client-go, e2e tests against a cluster); none of that surfaces in the three skills, which sit alongside the code rather than documenting what the code does.

READ THE FULL ANALYSIS＋

Why the mismatch. learn-session and learn-history are a generic Claude Code workflow pattern rather than anything OpenShift-specific — the same shape of skill turns up, under other names, in other repositories' own dev tooling. If you came to this page looking for oc or cluster automation, there isn't any here yet; what you get instead is a small, honest slice of how the oc team keeps its own coding agent calibrated.