docs: add pgro-status agent skill#48
Merged
Merged
Conversation
Standardised workflow for checking pgro health in a live cluster via kubectl. Covers an overview phase and per-replica detail phase, signals worth flagging, and pointers for investigating failures. Pulled out of repeated ad-hoc status checks. Cluster-specific identifiers (contexts, namespaces, etc.) are kept out of the skill so it works against any pgro deployment.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Standardised workflow for inspecting pgro health in a live cluster via
kubectl. Splits into an overview phase and a per-replica detail phase, lists signals worth flagging, and gives starting points for investigating failures (operator log bucketing, in-flight kopia Job logs, deployment init logs).Pulled out of repeated ad-hoc status checks I'd been running by hand. Cluster-specific identifiers (contexts, namespaces, customer names) are kept out of the skill so it works against any pgro deployment.
Lives under
.claude/skills/pgro-status/SKILL.mdso it travels with the repo and other engineers using Claude Code (or similar agent tooling that loads skills from the repo) get it automatically.