trace-change-impact
Skill1 starsChanged 27 days agoApache-2.0View on GitHub
Trace what a Terraform change touches: which blocks changed, how module variables and outputs changed, and which root modules reach a changed module. Use before editing or merging a module that other roots call, when the user asks "what does this change affect", "who uses this module", or "is this change breaking".
In this repository8 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- check-moduleSkill
- explain-planSkill
- fix-review-findingsSkill
- look-up-schemaSkill
- onboard-toolchainSkill
- review-moduleSkill
- writing-terraformSkill
The file
Files
Trace change impact
Find the blast radius of a change before it reaches a plan.
Call change_impact with:
path: a directory inside the project, relative to the project root. Changes are the working tree, staged and untracked.tffiles under it.base_ref: the git ref to compare against,HEADby default. The comparison runs against the merge base of the ref andHEAD, so pass the default branch to review a whole feature branch.
The result lists the changed blocks (added, modified or removed, a removed block located at its base file and line), each changed module's variable and output changes (added, removed, type or default changed), and every root module in the whole project that reaches a changed module, with its shortest module call path. It reads only git and the files; there is no plan or state.
Read the result as a contract check. A removed or retyped variable or output breaks every root in the list that sets or reads it. A new variable without a default breaks every caller. Name the affected roots and the call path, then say which ones need a plan before the change merges. Do not claim what a plan would print; that needs plan_digest on a rendered plan.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

