Skip to content

evrentan/observe-lens

v1.0.1Apache-2.0

Read-only investigation skills across CI pipelines (Jenkins, GitHub Actions), CD (Argo CD, Flux, Helm, Kubernetes), databases (PostgreSQL, MySQL, MongoDB) and telemetry (Grafana, Loki, Tempo, Prometheus).

observe-lens-cd

Read continuous-delivery state read-only to explain what is deployed where and whether it is healthy: Argo CD applications (sync and health status, deployed revision, sync history, failing resources, events, conditions), Flux kustomizations and Helm releases, Helm release history, and Kubernetes rollouts, pods, restarts and events through guarded read-only kubectl, helm and flux commands. Use this whenever the user asks whether a commit, image tag or fix is deployed to an environment, when a deploy happened or finished, why an app is OutOfSync, Degraded, Progressing or crash-looping, what changed in the last release, or whether a rollback happened, even if they do not say Argo CD, Flux, Helm or Kubernetes. Read-only: it never syncs, rolls back, restarts, scales or edits anything; it tells the user how. For build and test results use observe-lens-pipelines; for logs and metrics use observe-lens-telemetry.

Version
1.0.1
License
Apache-2.0
Compatibility
Python 3.11+ (standard library only) on macOS, Linux or Windows. Argo CD needs network access and an instance in ~/.config/observe-lens/cd; kubectl, helm or flux need those CLIs and a kube context (see references/setup.md).
Read SKILL.md at the source

Pinned to revision bb5531accd45, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.