opsmill/infrahub-skills

infrahub-common

Shared references and cross-cutting rules for all Infrahub skills — GraphQL syntax, .infrahub.yml format, and common patterns.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/opsmill/infrahub-skills --skill infrahub-common

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Infrahub Common References

This skill contains shared resources referenced by all other Infrahub skills. It is not meant to be invoked directly.

Contents

  • `graphql-queries.md` — Infrahub GraphQL query syntax,

filters, nested queries, and pagination patterns

  • `infrahub-yml-reference.md` — .infrahub.yml

configuration file format and field reference

  • `marketplace-reference.md` — Infrahub Marketplace:

reusing published schemas and collections via infrahubctl marketplace get, discovery with infrahubctl marketplace list / search / show, and airgap fallback. Reuse before modelling from scratch.

  • `netbox-vs-infrahub.md` — Field-by-field

migration appendix for engineers porting NetBox queries, templates, or overlay data

  • `metadata-lineage.md` — Value metadata (source,

owner, is_protected): what each field means, how to set it in object files, and why source does not control edit access

  • `profiles-and-templates.md` — The Profiles vs

Object Templates distinction and mechanics

  • `rules/` — Cross-cutting rules shared across skills:
  • Branch-first data CRUD (default to a branch, not the default branch)
  • Caching display labels in queries
  • Python environment and connectivity checks
  • Git integration and deployment patterns
  • Dry-running a changed .gql query against the live

schema before merge, and which infrahubctl command does it for a transform, check or generator

  • Recovery from partial repository syncs
  • Generated file protocol conventions
  • schema.graphql as `infrahubctl graphql

export-schema` output — re-exported, never hand-edited

  • Adopting generated protocols for typed SDK calls
  • Information-source priority (skill content first,

with a concrete last-resort procedure for consulting docs.infrahub.app on a genuine gap)

同じリポジトリから

関連する Skills

すべての Skills
opsmill
コミュニティ

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

1時間の導入数
2
GitHub Stars
27
更新日
11月9日
opsmill
コミュニティ

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

1時間の導入数
3
GitHub Stars
27
更新日
11月9日
opsmill
コミュニティ

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).

1時間の導入数
3
GitHub Stars
27
更新日
11月9日
opsmill
コミュニティ

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

1時間の導入数
3
GitHub Stars
27
更新日
11月9日