← ClaudeAtlas

planguard-comparelisted

Re-reviews only what changed since the last approved plan. Runs plan_diff.py on two Terraform plan JSONs (or two sets of Kubernetes manifests) and reports resources added, removed or changed, with attribute-level before and after values, sensitive values masked, and a re-review checklist. Use when the user says "what changed since the approved plan", "compare these two plans", "the plan changed after approval", "only re-review the delta", "diff the rendered manifests", or "did anything new sneak into this plan".
vivekbhange-hub/plan-guard-skill · ★ 0 · DevOps & Infrastructure · score 75
Install: claude install-skill vivekbhange-hub/plan-guard-skill
# planguard-compare: re-approve the delta, not the whole plan A plan gets approved on Tuesday, a teammate pushes a fix on Wednesday, and the plan applied on Thursday is not the plan anyone read. Reading everything again is slow, so people skim, and the skimmed change is the one that opens a port. `plan_diff.py` compares the approved plan with the current one and lists only what moved. ## Inputs - **Terraform:** two plan JSONs made with `terraform show -json plan.out > plan.json`, the last approved one and the current one. Keep the approved JSON with the change record; it can contain secrets, so it does not go into chat or a public ticket. - **Kubernetes:** two folders or files of rendered manifests (for example `helm template` output at the approved commit and now). - Fields to ignore for manifests, such as a chart version label that changes every release (`--ignore-field 'metadata.labels.helm.sh/chart'`). - Commands below say `python3`; on Windows use `python` (or `py -3`). ## Outputs - A drift report: counts of added, removed, changed and identical, a verdict (`identical`, `changed, no risk flags`, `re-approve required`), tables per section, attribute-level diffs, and a checkbox list of flagged items. - Terraform extras: Terraform core and provider constraint changes, output changes. - A short list for the reviewer: the items that need a fresh approval, and the ones that do not. ## Steps 1. **Confirm authorization.** Both inputs should be from infrastruct