opsmill/infrahub-skills

infrahub-planning-upgrades

Plans a version-by-version Infrahub upgrade path and scores each release's breaking changes against the user's repository and instance, producing UPGRADEPLAN.md.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/opsmill/infrahub-skills --skill infrahub-planning-upgrades

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Infrahub Upgrade Path Planner

Overview

Produces UPGRADE_PLAN.md: the route from the running Infrahub version to the target, one hop per minor version, with every breaking change in that range checked against this repository and, when reachable, this instance.

The plan describes how to upgrade; it does not upgrade. It never runs the upgrade, a schema load, or a branch write, and it never hands the user the upgrade command. It may run and show read-only probes. The user's deployment method (Docker Compose, Helm, Enterprise, Community) decides the exact commands, and the upgrade guide for that deployment owns them.

Versions, not editions. The plan covers a move to a later version within one edition. Switching between Community and Enterprise, in either direction, is not a version upgrade and the release notes do not cover it. Say so and point at <https://docs.infrahub.app/overview/community-vs-enterprise#migration-path> instead of planning it. A request that does both plans the version upgrade only and names the edition change as out of scope.

Write is granted for UPGRADE_PLAN.md only. Bash is granted for reading release notes with gh and for the read-only probes.

Project Context

This skill runs in a forked context and has no view of the parent conversation, so the user's request arrives verbatim as the arguments: the versions, and everything else the plan depends on, such as a pasted schema, the deployment method (step 6 picks the upgrade guide from it), the edition, and any pressure to "just run it". For example: /infrahub:planning-upgrades We run 1.9.2 on Docker Compose, Community, and want 1.10.0. Here is our schema: ...

With no target, ask for one. With no current version, read it from infrahubctl info (Infrahub Version:), and ask if the server is unreachable.

Workflow

  1. Fix the endpoints and the hops. Infrahub

supports upgrades only from the previous minor version (N-1), so 1.6.3 to 1.9.0 is three hops: 1.6 to 1.7, 1.7 to 1.8, 1.8 to 1.9. Never plan a jump across minors, even when the user asks for "one go". Patches are different: one upgrade applies every pending migration in order, so 1.9.1 to 1.9.6 is a single hop, and a minor hop can start from any patch of the previous minor (1.9.1 to 1.10.0). Rolling up patches within the current minor first (1.10.8 to 1.10.10) is fine as its own section, not a requirement.

  1. **Enumerate every release in the range, patches

included, and read each one's notes.** Read rules/sources-enumerate-every-hop.md before fetching anything: breaking changes ship in patch releases, and no machine-readable flag marks them.

  1. Inventory the repository. Schema YAML,

.infrahub.yml, GraphQL queries, and the Python checks, generators, and transforms. If an instance is reachable, confirm it with infrahubctl info (connectivity-server-check) and read live data through the MCP read tools (mcp-tools). The instance is optional; the repository is not.

  1. Give every finding a verdict and back it. Read

rules/impact-verdict-needs-evidence.md before filling the Affected and Evidence columns.

  1. Probe, read-only. Read

rules/safety-read-only-probes.md before running or showing any command, and again if the user asks you to run the upgrade.

  1. Write `UPGRADE_PLAN.md` in the shape below.

Each hop's steps are prose: take a backup, clear the before findings, upgrade to the hop's target following the upgrade guide, clear the during and after findings. Link the guide rather than transcribing it, picking the edition page when you know the edition:

  • overview: <https://docs.infrahub.app/deploy-manage/maintain-upgrade/upgrade/overview>
  • Community: <https://docs.infrahub.app/deploy-manage/maintain-upgrade/upgrade/community>
  • Enterprise: <https://docs.infrahub.app/deploy-manage/maintain-upgrade/upgrade/enterprise>

Plan Format

One ## section per hop, in ascending order, with the hop's two versions in the heading (## 1.9 -> 1.10). Each hop carries one findings table with these nine columns, in this order:

ChangeReleaseKindSeverityWhenAffectedEvidenceActionSource
ColumnValues
Releaseone version, X.Y.Z, never a range
Kindbreaking or preparation
Severitycritical, warning, or info
Whenbefore, during, or after the hop
Affectedyes, no, or unknown

What each value means, and a worked example, are in reference.md. Read it before writing the first row.

Rule Categories

CategoryPrefixRules
Sourcessources-sources-enumerate-every-hop
Impactimpact-impact-verdict-needs-evidence
Safetysafety-safety-read-only-probes

Supporting References

an example plan. Read at step 6.

index.

from this repository

More skills

All skills
opsmill
Community

infrahub-analyzing-diagnostics

Analyze an already-collected infrahub-collect diagnostic bundle — traceback and failure triage across service logs, incident correlation, and known-issue matching against opsmill/infrahub GitHub issues. TRIGGER when: the user says they collected a diagnostic bundle, gives you a bundle path, or pastes bundle contents — and asks what's wrong, wants the logs or tracebacks analyzed, asks "what does this bundle say", wants errors triaged/correlated, or asks whether a crash is a known issue. DO NOT TR

1h installs
2
GitHub stars
27
Updated
Nov 9
opsmill
Community

infrahub-analyzing-data

Analyzes and correlates live Infrahub data via the MCP server — answers operational questions, detects drift, and investigates impact. TRIGGER when: querying infrastructure data, checking compliance, investigating change impact, producing ad-hoc reports. DO NOT TRIGGER when: writing automated checks, building transforms, designing schemas, populating data files, planning an Infrahub version upgrade (use infrahub-planning-upgrades). ALWAYS pass the user's question verbatim as args — this skill ru

1h installs
3
GitHub stars
27
Updated
Nov 9
opsmill
Community

infrahub-auditing-repo

Audits an Infrahub repository against best practices and rules, producing a structured compliance report. TRIGGER when: reviewing repo for compliance, onboarding to existing project, pre-deployment validation, catching issues. DO NOT TRIGGER when: creating schemas, writing checks/generators, querying live data, populating objects, planning an Infrahub version upgrade (use infrahub-planning-upgrades).

1h installs
3
GitHub stars
27
Updated
Nov 9
opsmill
Community

infrahub-collecting-diagnostics

Collect a redacted local diagnostic bundle (logs, config, version, state) for an OpsMill expert hand-off. TRIGGER when: Infrahub is broken/failing/erroring, the user asks for help debugging, wants to collect logs/diagnostics, prepares a hand-off for OpsMill support, or reports a crash/timeout/connection issue (upgrade failure, stuck branch, container CrashLoopBackOff, 500s, OOM). DO NOT TRIGGER when: debugging a check, transform, generator, menu, or schema in the repository (use the infrahub-man

1h installs
3
GitHub stars
27
Updated
Nov 9