drift

Use when asked whether what is running matches what is in git, after a deploy, when a rollout seems stuck, or when someone changed infrastructure by hand.

Skill by Srimukh99

IndexedMIT

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/srimukh99-drift

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Use when asked whether what is running matches what is in git, after a deploy, when a rollout seems stuck, or when someone changed infrastructure by hand. Compares desired state with current state and tracks drift over time.

Use cases: devops

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found
Runs as: Python package

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/drift

What's inside

Skill name: drift
Description: Use when asked whether what is running matches what is in git, after a deploy, when a rollout seems stuck, or when someone changed infrastructure by hand. Compares desired state with current state and tracks drift over time.
License: MIT
Instructions: 25 lines in SKILL.md · view on GitHub

Before installing

Ships executable scripts

Files (2)

SKILL.md
drift_check.py · scripts/

SKILL.md (first lines)

# drift

Desired state is git: Terraform, manifests, Helm values, GitOps apps. Current state is what is live. This skill finds the gap and records it.

## Do

1. Run `python3 <this skill folder>/scripts/drift_check.py` with any of `--k8s-dir deploy/`, `-n <namespace>`, `--tf-dir infra/`. It is read-only: it runs `terraform plan`, `kubectl diff` and `kubectl get` only, and skips tools that aren't installed.
2. Read the summary:
   - **terraform**: resources to create, update, replace or destroy, and changes made outside Terraform.
   - **manifests**: resources whose live spec differs from the files.
   - **rollouts**: desired vs updated vs ready replicas, stuck rollouts, and specs the controller hasn't observed yet.
   - **pods**: crash loops, image pull errors, OOM kills, unschedulable pods.
   - **gitops / helm**: Argo CD apps not synced or healthy, Flux not ready, failed Helm releases.
3. Every run is appended to `.rubric/state.jsonl` (commit SHA, what drifted). Run `--history` to see when drift first appeared.

## Correcting drift

1. Decide which side is right. If the live change was an emergency fix, put it in git first.
2. Correct through the normal path: a PR, then `terraform apply` or a GitOps sync. Never hand-edit live resources to "fix" drift.
3. Re-run drift and show it in sync (`ship`).
4. For regulated systems, log the correction as a change (`reg-audit`).

Never run `apply`, `sync`, `delete` or `rollout undo` without the user's explicit go-ahead.

From Srimukh99/rubric, MIT.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Oct 2, 2026 (26 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/Srimukh99/rubric
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from Srimukh99

Cite this page

drift skill. Agent Mart. https://agentmart.dev/skills/srimukh99-drift (last updated 2026-10-24)