kuberocketci/krci
Agent skills for delivering software on the KubeRocketCI platform, from the ticket to production: for BA, PO, PM, developers, QA, and DevOps engineers
Why an environment is unhealthy, out of sync, or shows nothing deployed, and who owns the fix. Use when an environment or its Argo CD app is Degraded, Unknown, Missing, OutOfSync, or on version NaN, a sync failed, the environment failed to create, or pods crash-loop, stay Pending, or hit ImagePullBackOff. Not for a failed build or review run, or a pending quality gate, which krci-overview routes.
Foundation for delivering software on KubeRocketCI (KRCI, formerly EDP), from ticket to production, for every role. Use when a request mentions KubeRocketCI, krci, or the portal; projects or codebases, branches, builds, or Tekton pipeline runs; deployments, environments or stages, or Argo CD applications of the platform; quality gates, autotests, or promotion; where a ticket's change is deployed; a custom pipeline or the chart in deploy-templates/; and before running krci or kubectl against a tenant. Covers the lifecycle, roles, vocabulary, tools, preflight, safety contract, and ownership verdict.
The implementation status of a story by its tracker key, per project — whether it merged, its first version, and which environments run it. Use when asked about the status or progress of a story or ticket key, which version contains it, or its deployment. Not for why an environment itself is unhealthy or empty, which krci-debug-environment covers.