Przejdź do treści
Biblioteka skilli
DevOps i chmura · Automatyzacja

bumping-terraform

/bumping-terraform

Aktualizuje nieaktualne providery Terraform lub OpenTofu, przypięte wersje CLI i lockfile'e w modułach głównych.

Repozytorium
skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
25.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 25.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Aktualizuje nieaktualne providery Terraform lub OpenTofu, przypięte wersje CLI i lockfile'e w modułach głównych.

Oryginalny opis (EN)

Use when Terraform or OpenTofu providers, CLI pins, or lockfiles are outdated or behind; bump or upgrade them across root modules.

Jak działa

  1. Conversational requests
  2. Conventions for every run
  3. Core principle
  4. Scope
  5. Orchestration Plan
Sekcje z nagłówków SKILL.md, w oryginale · 208 linii, 1 793 słów
Podgląd SKILL.md
---
name: bumping-terraform
description: "Use when Terraform or OpenTofu providers, CLI pins, or lockfiles are outdated or behind; bump or upgrade them across root modules."
allowed-tools: ["Bash", "Read", "Grep", "Glob", "Edit", "Write", "AskUserQuestion"]
---

# Bumping Terraform

Find the root modules, move every declaration of a version together,
refresh each root module's lock file without narrowing it, and verify
the selected version changed. This skill classifies the request and hands
it to one of three skills; the conventions below apply to whichever runs.

## Conversational requests

The three slash-command skills are gated, so the model cannot invoke them.
Match the request to one, then read its file and follow it from its
Procedure through its Output, taking its arguments from the request's
wording:

- A provider to move: `../bump-provider/SKILL.md`.
- The CLI version to move: `../bump-terraform/SKILL.md`.
- Locks to refresh inside existing constraints:
  `../refresh-lock/SKILL.md`.

A request that names none ("everything here is behind") is a provider
bump with no provider named unless the user says the CLI: list the
declared providers and ask which (headless default: stop). One run does
one of them; offer the others as next steps.

## Conventions for every run

- Name the current branch in the plan. Before the run's first edit, run
  `git status --porcelain` and print the result: that list is the
  changes the run did not make. Never rely on it from memory in later
  commands. Commit only this run's paths with `git commit -- <paths>`,
  after `git add <path>` for any new file such as a lock file (`git
  commit -- <untracked path>` fails). Stop when a path to commit is
  already in the recorded list. Also before the first edit, record each
  gate's result on the original tree, as [Verification
  gates](../../references/lock-and-init.md#verification-gates) describes.
- Script paths: `../../scripts/lockctl.py` resolves from a skill's
  directory (a reference writes `../scripts/`). Print the absolute path
  once and write it literally in each command, since shell variables do
  not persist between Bash calls.
- Run `init`, `providers lock`, `lockctl.py diff`, each repository gate,
  and `git commit` in separate Bash calls, one command per call. Read
  that command's returned exit status before continuing. Read long
  output from the host's saved result separately; a display filter or
  trailing command can hide the operation's failure.
- After `git commit`, read it back in separate calls: `git show
  --name-status --format=%s HEAD` lists exactly this run's paths, and
  `git status --porcelain` adds nothing to the recorded list beyond
  `init`'s `.terraform/` cache. Report the commit only when both hold;
  otherwise report what differs.
- Commit bodies say what moved and why, and cite release notes at the
  tag the registry reported only when the run fetched that page; with
  none, the body names no link. Take the subject format from the
  project's AGENTS.md or CLAUDE.md. Write them per
  `../../references/prose-rules.md`.
- Write each commit message to a temp file with the file tool and commit
  with `git commit -F <file> -- <paths>`. Messages quote registry text
  (sources, tags, links), which a double-quoted `-m` or a heredoc would
  expand or end early.
- Commit messages carry no `Co-Authored-By`, no "Generated with" or other
  tool trailers, and no emoji.
- Where there is no interactive question tool (Codex, headless runs),
  state each question in the reply with the narrower answer as the
  default (fewest modules, `--no-commit`), without remarking that no
  question tool exists. A headless run presents the
  plan and stops, unless the request itself authorises the edit ("go
  ahead and bump it"); that covers the edit only, never a commit or
  push.
- Reply in the shape each skill's Output declares, as plain text outside
  any code fence, with plain bullets and no bold (never
  `- **Label:** ...`), and no section that would hold nothing. Name paths
  relative to the repository, never local absolute or temporary paths,
  and name tools by name (`terraform`), never by install path. Name no
  helper script in a reply; say what it found.
- Where no question tool exists, close with `Next steps:` and a plain
  bulleted list of the options, in that form every time, then stop. A
  stopped run is the exception: it has no panel and no `Next steps:`
  list.
- A reply's `## Layout` names what the user can act on: the roots and
  children found and any settled classification. Name the driving tool
  only when both `terraform` and `tofu` are present. Leave out the branch
  and any tool that is not installed.
- Name no version the registry has not confirmed, and make no claim about
  what a newer release changes (such as a major jump) before one is
  confirmed. A version the user named that the registry cannot confirm
  (unreachable, or absent from the release list) is a stopped run unless
  the user said they confirmed it; the next step offers that confirmation
  or access to the registry.
- Output rules for every reply: state results, not the rules behind them.
  Do not mention commit-message rules, trailers, or this skill's
  conventions. Do not recap a default taken ("I've taken the default"); a
  next-step option "stop here" is fine. Do not remark on the missing question tool. Do not
  write "X, not Y" contrasts or filler such as "nothing needed
  classifying by you". A bullet states a finding, not scope the plan
  already gave. The hero is the line the skill's shape gives with
  nothing appended. A completed report states gate results in
  `## Verification`; a halted run uses the stopped form below. Every
  reply omits what the repository lacks ("no other file pins the CLI", "no child modules
  found", "tflint isn't installed", "the repository defines no other
  gates") and never states what the run will do on its own later ("I'll
  run the audit again"). A completed `--no-commit` report does not say
  nothing was committed.
- A run that cannot proceed (nothing declared, no version named and the
  release list unreachable, a dirty tree it cannot work around, a lock
  that failed after the edits, a gate the edits plausibly broke) ends
  with `⚠ Stopped: <one result sentence>`, then the step the user must
  take. The result sentence says what state the repository is in: `so
  nothing was edited` before the first edit, or `so nothing was
  committed` after it. A run stopped after its edits leaves them in the
  working tree, and the step offers reverting them (`git restore --
  <paths>`) first.

  The reply has no sections, no recap, and no numbered next-step list.
  The step is one or two sentences and ends with its request; it states
  nothing the run will do afterwards ("I'll show the plan", "then I'll
  rerun it", "so I can ..."). A stop caused by missing configuration says
  so once, in the result sentence, and does not list the files or commits
  searched for.

  Bullets are optional, at most three, and each states a repository fact
  the step depends on, usually the declared pins that disagree. Write no
  bullets when there is no such fact. Never write a bullet about:

  - lock files, backends, call graphs, or the installed CLI, or whether a
    pin or installed version satisfies the target;
  - the branch, history, untracked files, or the driving tool;
  - what the run would do after the edit, or anything the repository lacks
    ("no lock file", "no CI file runs providers lock");
  - a question or request.

  Exceptions: the result sentence names roots outside `--root-module` that
  call a child module the run would edit, and a stop after the edits may
  carry one bullet with the new constraint and the lock's selected version
  as they stand ("the lock selects 3.7.0 with 1 h1 checksum, 2 before").
  Name no sandbox or network block; say the registry or mirror was
  unreachable.

  Reply in this shape, as plain text outside any code fence, with plain bullets, no bold (never `- **Label:** ...`), and no local paths:

  ```text
  ⚠ Stopped: I could not confirm hashicorp/aws 6.57.0 because registry.terraform.io was unreachable, so nothing was edited.

  Tell me you confirmed 6.57.0 yourself, or allow registry.terraform.io.

  - envs/prod and modules/network both declare hashicorp/aws, at ~> 6.56.0 and ~> 6.55.0, so the pins disagree.
  ```

  After edits, with the lock restored and the constraint edit remaining:

  ```text
  ⚠ Stopped: infra/prod cannot resolve random 3.7.0 from its mirror, so nothing was committed.

  Revert the constraint edit with `git restore -- infra/prod/versions.tf`, or supply the required provider packages.

  - infra/prod declares ~> 3.7.0; its committed lock selects 3.6.0 with 2 h1 records.
  ```

- `--audit-only` writes nothing and is a result, not a stop. Its hero is
  `Audit only: <result>` with no `⚠`, the skill's own sections follow
  (omit the empty ones), and no sentence restates that nothing was
  written. In an audit `## Held back` lists only what a constraint or
  guard is already blocking, never constraints that merely permit a
  newer release. An audit with nothing to audit (no Terraform files) is a
  stopped run.
- A target the user confirmed is reported as "confirmed by you", with no
  reason attached. `## Drift` states only what `## Sites` and `## Locks`
  do not already say.
- When a confirmed target crosses a major version, link the project's
  upgrade guide in the report, or say none was found.

## Core principle

Constraints from every module in a configuration must all be satisfied at
once, so the unit of work is the configuration, not the file. Every
declaration moves in one commit, or none does.

## Scope

The current repository. Discover its root modules and confirm the set with
the user when there is more than one. When `--root-module` limits the run, list every root outside it that
calls a child module the run would edit (or declares the target pin). Such a root would be left
inconsistent, its lock failing `init`, so stop and name them, or widen the scope on the user's yes
(headless: stop). Never widen scope as a side effect:
no repository-wide operator normalising, no invented platform names,
no reformatting of modules the change did not touch.

## Orchestration Plan

Enter plan mode before the first edit. In Claude Code call `EnterPlanMode`; in Cursor, Codex, or Gemini use `/plan` or `Shift+Tab`. Where plan mode is unavailable, present the plan as text.

Present a plan covering:

- The root modules in scope, and any directory whose classification the
  user settled.
- The target version, and the evidence it exists.
- Every pin site to be edited, the operator each one keeps, and the
  sites left alone with the reason.
- Which lock files will be refreshed, each provider's `h1:` count, and
  any platform names declared by the repository or confirmed by the user.
- The commit this produces (constraints and locks together) and whether
  it will be pushed.
- Drift found that this run will not fix.

Wait for approval, then exit plan mode before the first edit. Without plan
mode, finish discovery, resolution, and inventory, and confirm scope with
the user before writing anything. Headless, the plan is the reply.

Pliki w paczce (2)
  • SKILL.md 11 KB
  • agents/openai.yaml 1 KB

Wersje

W bazie nie ma innych skilli o nazwie bumping-terraform.

Migawka bazy z 13.11.2026 · wersja paczki 92d9e15ad919 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100terraform-bumping-terraform
    Podnosi wersje providerów, przypięć CLI i lockfile'i Terraform lub OpenTofu w modułach root, gdy są przestarzałe.
  • 100bump-provider
    Aktualizuje jednego dostawcę Terraform lub OpenTofu w wielu modułach i odświeża lockfile'e w katalogach głównych, nie tracąc platform.
  • 90terraform
    Pomaga zmieniać repozytorium Terraform lub OpenTofu: providery, moduły, zasoby, stan, zmienne i plany infrastruktury.
  • 100terraform-helper
    Pomaga w pracy z plikami .tf w Terraform i OpenTofu: HCL, providery, moduły, zarządzanie stanem i polecenia CLI.
  • 100opentofu
    Obejmuje OpenTofu, otwartoźródłowy fork Terraform: HCL, providery, zarządzanie stanem, moduły oraz migrację z Terraform i różnice między oboma narzędziami.
  • 100terraform
    Konfiguruje moduły Terraform i OpenTofu, testy, zarządzanie stanem i przegląd HCL dla wielu środowisk infrastruktury jako kodu.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.