all publishers

opsmill

@opsmill source repo

164 published skills · page 1 of 2

  1. ▌
    Speckit Specify 3 · opsmill
    Create or update the feature specification from a natural language feature description.
    544 repo stars
  2. ▌
    Speckit Plan 4 · opsmill
    Execute the implementation planning workflow using the plan template to generate design artifacts.
    544 repo stars
  3. ▌
    Speckit Tasks 3 · opsmill
    Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
    544 repo stars
  4. ▌
    Infrahub Managing Objects 3 · opsmill bundle
    Creates and manages Infrahub object data YAML files for populating infrastructure instances — devices, locations, organizations, and modules. TRIGGER when: creating device instances, populating data files, defining locations or organizations, adding infrastructure objects. DO NOT TRIGGER when: designing schemas, writing Python checks/generators, querying live data.
    544 repo stars
  5. ▌
    Infrahub Managing Schemas 3 · opsmill bundle
    Creates, validates, formats, and modifies Infrahub schema YAML files — nodes, generics, attributes, relationships, and extensions. Also checks the Infrahub Marketplace for an existing published schema to reuse before modelling a domain from scratch. TRIGGER when: designing data models, adding schema nodes, validating schema definitions, planning schema migrations, looking for an existing/off-the-shelf schema or checking the marketplace for a domain (DCIM, location, routing, etc.), modeling file objects / attachments / uploads (storing PDFs, diagrams, images, certificates, documents as Infrahub objects), formatting or tidying schema files, normalising / canonicalising schema key order, cleaning up noisy schema diffs where every edit reshuffles keys, or running `infrahubctl schema format` (including as a CI gate). DO NOT TRIGGER when: populating data objects, writing checks/generators/transforms, querying live data.
    544 repo stars
  6. ▌
    Infrahub Managing Generators 3 · opsmill bundle
    Creates Infrahub Generators — design-driven automation that builds infrastructure objects from templates and topology definitions. TRIGGER when: building design-to-implementation workflows, auto-creating objects from templates, topology-driven generation. DO NOT TRIGGER when: designing schemas, writing data transforms, querying live data, populating static data files.
    544 repo stars
  7. ▌
    Infrahub Managing Transforms 3 · opsmill bundle
    Creates Infrahub transforms that convert data into JSON, text, CSV, or device configs using Python or Jinja2 templates, with YAML-driven tests. TRIGGER when: building config generation, data export, format conversion, Jinja2 templates, artifact pipelines, writing or running tests for a transform. DO NOT TRIGGER when: designing schemas, writing validation checks, creating generators, querying live data.
    544 repo stars
  8. ▌
    Infrahub Auditing Repo 3 · opsmill bundle
    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.
    544 repo stars
  9. ▌
    Infrahub Analyzing Data 3 · opsmill bundle
    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. ALWAYS pass the user's question verbatim as args — this skill runs in a forked context and cannot see the parent conversation. Invoking without args will fail.
    544 repo stars
  10. ▌
    Infrahub Managing Menus 3 · opsmill bundle
    Creates Infrahub custom navigation menus for the web UI sidebar, organizing node types into logical groups. TRIGGER when: designing sidebar menus, grouping node types in UI, customizing Infrahub web interface navigation. DO NOT TRIGGER when: designing schemas, writing checks or transforms, populating data objects.
    544 repo stars
  11. ▌
    Infrahub Managing Checks 3 · opsmill bundle
    Creates Infrahub check definitions — Python validation logic, GraphQL queries, and YAML-driven tests for proposed change pipelines. TRIGGER when: writing validation checks, creating Python checks, building data quality guards for proposed changes, writing or running tests for a check. DO NOT TRIGGER when: designing schemas, querying live data, building transforms or generators.
    544 repo stars
  12. ▌
    Infrahub Common 3 · opsmill bundle
    Shared references and cross-cutting rules used by all Infrahub skills. Contains GraphQL query syntax, .infrahub.yml configuration format, and common rules for git integration, display label caching, and Python environment setup. DO NOT TRIGGER directly — loaded automatically by other Infrahub skills when they need shared references.
    544 repo stars
  13. ▌
    Speckit Checkpoint Commit 2 · opsmill
    Commit the artifacts produced by the speckit phase that just completed
    544 repo stars
  14. ▌
    Speckit Review Run 3 · opsmill
    Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.
    544 repo stars
  15. ▌
    Pr 2 · opsmill
    Opens a pull request, publishing the current branch as a PR. TRIGGER when: the user wants to open a pull request, publish the current branch as a PR, or take the current work through to an open PR. DO NOT TRIGGER when: only committing changes → commit; babysitting CI after the PR is already open → monitoring-pull-requests.
    544 repo stars
  16. ▌
    Commit 2 · opsmill
    Stages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream. TRIGGER when: the user wants to commit, save, or check in the current changes. DO NOT TRIGGER when: opening a pull request → pr.
    544 repo stars
  17. ▌
    Rebase 2 · opsmill
    Rebases a feature branch onto its latest base, resolving conflicts while preserving the intent of local changes, optionally force-pushing and watching CI afterward. TRIGGER when: the user wants to rebase a feature branch, update a branch against its base, or replay local work on top of the latest upstream. DO NOT TRIGGER when: merging a release branch into dev → merging-branches; only watching CI on an already-open PR → monitoring-pull-requests.
    544 repo stars
  18. ▌
    Grilling Ideas 2 · opsmill
    Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.
    544 repo stars
  19. ▌
    Creating Issues 2 · opsmill
    Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.
    544 repo stars
  20. ▌
    Monitoring Pull Requests 2 · opsmill
    Watches an open pull request's CI until green and fixes failing checks. TRIGGER when: the user wants to watch a pull request's CI, babysit a PR until it goes green, or fix failing CI checks on an open PR. DO NOT TRIGGER when: opening the PR in the first place → pr; rebasing the branch onto its base → rebase.
    544 repo stars
  21. ▌
    Speckit Plan 3 · opsmill
    Execute the implementation planning workflow using the plan template to generate design artifacts.
    544 repo stars
  22. ▌
    Speckit Tasks 2 · opsmill
    Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
    544 repo stars
  23. ▌
    Speckit Analyze 2 · opsmill
    Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
    544 repo stars
  24. ▌
    Speckit Clarify 2 · opsmill
    Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
    544 repo stars
  25. ▌
    Speckit Specify 2 · opsmill
    Create or update the feature specification from a natural language feature description.
    544 repo stars
  26. ▌
    Speckit Converge 2 · opsmill
    Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
    544 repo stars
  27. ▌
    Speckit Checklist 2 · opsmill
    Generate a custom checklist for the current feature based on user requirements.
    544 repo stars
  28. ▌
    Speckit Implement 3 · opsmill
    Speckit Implement
    544 repo stars
  29. ▌
    Speckit Constitution 2 · opsmill
    Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
    544 repo stars
  30. ▌
    Speckit Taskstoissues 2 · opsmill
    Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
    544 repo stars
  31. ▌
    Speckit Opsmill Retrospect 3 · opsmill
    Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.
    544 repo stars
  32. ▌
    Infrahub Common 2 · opsmill bundle
    Shared references and cross-cutting rules for all Infrahub skills — GraphQL syntax, .infrahub.yml format, and common patterns. DO NOT TRIGGER directly — loaded automatically by other Infrahub skills when they need shared references.
    544 repo stars
  33. ▌
    Infrahub Auditing Repo 2 · opsmill bundle
    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.
    544 repo stars
  34. ▌
    Infrahub Analyzing Data 2 · opsmill bundle
    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. ALWAYS pass the user's question verbatim as args — this skill runs in a forked context and cannot see the parent conversation. Invoking without args will fail.
    544 repo stars
  35. ▌
    Infrahub Importing Data 2 · opsmill bundle
    Converts CSV/TSV inputs into Infrahub object YAML and loads them onto a fresh branch. Handles a single file, a folder of files, an explicit list of paths, and one-big-denormalized-sheet exports. TRIGGER when: importing CSV, loading CSV/TSV into Infrahub, ingesting spreadsheet data, converting CSV to Infrahub objects, splitting a denormalized CSV across multiple kinds. DO NOT TRIGGER when: running `infrahubctl import load` against an LDJSON dump (different format and tool), designing or modifying schemas (this skill is read-only against the schema and fails closed on unmapped columns), exporting data from Infrahub (use `infrahubctl object get -o csv` for single-kind export), or ingesting JSON/XLSX (v1 is CSV+TSV only).
    544 repo stars
  36. ▌
    Infrahub Managing Menus 2 · opsmill bundle
    Creates Infrahub custom navigation menus for the web UI sidebar, organizing node types into logical groups. TRIGGER when: designing sidebar menus, grouping node types in UI, customizing Infrahub web interface navigation. DO NOT TRIGGER when: designing schemas, writing checks or transforms, populating data objects.
    544 repo stars
  37. ▌
    Infrahub Managing Checks 2 · opsmill bundle
    Creates Infrahub check definitions — Python validation logic, GraphQL queries, and YAML-driven tests for proposed change pipelines. TRIGGER when: writing validation checks, creating Python checks, building data quality guards for proposed changes, writing or running tests for a check. DO NOT TRIGGER when: designing schemas, querying live data, building transforms or generators.
    544 repo stars
  38. ▌
    Infrahub Managing Objects 2 · opsmill bundle
    Creates and manages Infrahub object data YAML files for populating infrastructure instances — devices, locations, organizations, and modules. TRIGGER when: creating device instances, populating data files, defining locations or organizations, adding infrastructure objects. DO NOT TRIGGER when: designing schemas, writing Python checks/generators, querying live data.
    544 repo stars
  39. ▌
    Infrahub Managing Schemas 2 · opsmill bundle
    Creates, validates, and modifies Infrahub schema YAML files — nodes, generics, attributes, relationships, and extensions. TRIGGER when: designing data models, adding schema nodes, validating schema definitions, planning schema migrations, modeling file objects / attachments / uploads (storing PDFs, diagrams, images, certificates, documents as Infrahub objects). DO NOT TRIGGER when: populating data objects, writing checks/generators/transforms, querying live data.
    544 repo stars
  40. ▌
    Infrahub Reporting Issues 2 · opsmill bundle
    Reports bugs and feature requests against the right Infrahub-ecosystem GitHub repository. Classifies the request, routes it (with the main `opsmill/infrahub` repo as the safe fallback when in doubt), searches for existing duplicates, gathers conservative environment info for bugs, and prepares the issue for the user to review before any submission. TRIGGER when: user wants to report a bug, file an issue, request a feature, open a ticket, or escalate a problem in any opsmill/infrahub-* project (SDK, Ansible, VS Code, MCP, Helm, schema-library, sync, backup, nornir, skills). DO NOT TRIGGER when: the user wants to fix the bug themselves locally, write a test, or debug code without filing.
    544 repo stars
  41. ▌
    Infrahub Managing Generators 2 · opsmill bundle
    Creates Infrahub Generators — design-driven automation that builds infrastructure objects from templates and topology definitions. TRIGGER when: building design-to-implementation workflows, auto-creating objects from templates, topology-driven generation. DO NOT TRIGGER when: designing schemas, writing data transforms, querying live data, populating static data files.
    544 repo stars
  42. ▌
    Infrahub Managing Transforms 2 · opsmill bundle
    Creates Infrahub transforms that convert data into JSON, text, CSV, or device configs using Python or Jinja2 templates, with YAML-driven tests. TRIGGER when: building config generation, data export, format conversion, Jinja2 templates, artifact pipelines, writing or running tests for a transform. DO NOT TRIGGER when: designing schemas, writing validation checks, creating generators, querying live data.
    544 repo stars
  43. ▌
    Infrahub Collecting Diagnostics 2 · opsmill bundle
    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: filing a public GitHub issue (use infrahub-reporting-issues), or running operational queries (use infrahub-analyzing-data).
    544 repo stars
  44. ▌
    Speckit Implement 2 · opsmill
    Speckit Implement
    544 repo stars
  45. ▌
    Quality Gates 2 · opsmill bundle
    Shared in-workflow quality gates for code/PR skills — the gate model, trust tiers, and the three primitives (evidence-before-done, independent judge, anti-gaming). DO NOT TRIGGER directly — referenced by consumer skills via relative path.
    544 repo stars
  46. ▌
    Speckit Infrahub Speckit Route Plan 2 · opsmill
    Hook command — runs before the active integration's speckit plan command in Infrahub projects. Invokes the matching infrahub-managing-* skill so Phase 0 research and data-model design are grounded in authoritative Infrahub reference material.
    544 repo stars
  47. ▌
    Speckit Infrahub Speckit Route Specify 2 · opsmill
    Hook command — runs before the active integration's speckit specify command in Infrahub projects. Detects .infrahub.yml, classifies artifact type, gates skill invocation, and emits the template-override directive that the core specify skill consumes.
    544 repo stars
  48. ▌
    Speckit Infrahub Speckit Route Implement 2 · opsmill
    Hook command — runs before the active integration's speckit implement command in Infrahub projects. Invokes the matching infrahub-managing-* skill for each artifact type that tasks.md touches, so implementation code follows authoritative Infrahub patterns and conventions.
    544 repo stars
  49. ▌
    Creating Prd 2 · opsmill
    Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.
    544 repo stars
  50. ▌
    Speckit Git Feature 2 · opsmill
    Validate Jira/JPD ticket reference and create a feature branch
    544 repo stars
  51. ▌
    Opsmill Dev Fixing Bugs 2 · opsmill
    Implements and validates the fix for a bug once a failing reproduction test exists. TRIGGER when: a bug has a failing reproduction test and you are ready to make it pass, implementing the root-cause fix, the final step of the bug-fixing pipeline. DO NOT TRIGGER when: no reproduction test exists yet → opsmill-dev-test-driving-bugs; still diagnosing, or asked to fix a bug with no analysis or reproduction test yet → opsmill-dev-analyzing-bugs.
    544 repo stars
  52. ▌
    Opsmill Dev Analyzing Bugs 2 · opsmill
    Performs root-cause analysis of a bug — from a GitHub issue, an issue URL, or a free-text description — before any reproduction or fix is written. TRIGGER when: triaging or diagnosing a bug, investigating why something misbehaves, an issue number/URL handed over for analysis, needing the root cause before touching code. DO NOT TRIGGER when: a failing reproduction test already exists and you are ready to fix → opsmill-dev-fixing-bugs; writing that reproduction test → opsmill-dev-test-driving-bugs; capturing a new bug as a ticket → opsmill-dev-creating-issues.
    544 repo stars
  53. ▌
    Speckit Opsmill Retrospect 2 · opsmill
    Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.
    544 repo stars
  54. ▌
    Opsmill Dev Test Driving Bugs 2 · opsmill
    Writes a single failing test that reproduces a bug after its root-cause analysis is complete, before any fix is written. TRIGGER when: a bug has a completed root-cause analysis and you need the failing reproduction test, writing a test that proves a bug exists, the second step of the bug-fixing pipeline. DO NOT TRIGGER when: still triaging or diagnosing the bug → opsmill-dev-analyzing-bugs; implementing the fix once the test exists → opsmill-dev-fixing-bugs; general feature test-first work → superpowers test-driven-development.
    544 repo stars
  55. ▌
    Speckit Plan 2 · opsmill
    Execute the implementation planning workflow using the plan template to generate design artifacts.
    544 repo stars
  56. ▌
    Speckit Review Run 2 · opsmill
    Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.
    544 repo stars
  57. ▌
    Speckit Review Code 2 · opsmill
    General code quality review — project guideline compliance, bug detection, code quality analysis.
    544 repo stars
  58. ▌
    Speckit Critique Run 2 · opsmill
    Perform a dual-lens critical review of the specification and plan from both product strategy and engineering risk perspectives before implementation.
    544 repo stars
  59. ▌
    Speckit Opsmill Auto 2 · opsmill
    Run the full speckit workflow end-to-end — specify, plan, critique, tasks, implement, review — making all decisions autonomously. Stops before extract; run that manually.
    544 repo stars
  60. ▌
    Speckit Opsmill Prep 2 · opsmill
    Run the speckit preparation phases end-to-end — specify, plan, critique, tasks — making all decisions autonomously. Stops before implementation.
    544 repo stars
  61. ▌
    Speckit Review Tests 2 · opsmill
    Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.
    544 repo stars
  62. ▌
    Speckit Review Types 2 · opsmill
    Type design analysis — encapsulation, invariant expression, usefulness, and enforcement.
    544 repo stars
  63. ▌
    Speckit Review Errors 2 · opsmill
    Error handling review — silent failure detection, catch block analysis, error logging.
    544 repo stars
  64. ▌
    Speckit Opsmill Extract 2 · opsmill
    Extract knowledge, guidelines, and ADRs from one or more completed spec directories into the project documentation system.
    544 repo stars
  65. ▌
    Speckit Opsmill Summary 2 · opsmill
    Produce a flow-level summary of the current Claude Code session — executive summary, chronological timeline, and outcomes — written into the active feature directory next to spec.md / plan.md.
    544 repo stars
  66. ▌
    Speckit Review Comments 2 · opsmill
    Code comment accuracy verification, documentation completeness assessment, comment rot detection.
    544 repo stars
  67. ▌
    Speckit Review Simplify 2 · opsmill
    Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.
    544 repo stars
  68. ▌
    Speckit Opsmill Implement 2 · opsmill
    Run the speckit implementation phase chunk-by-chunk in clean-context subagents, then review, then produce a final report. Picks up from an existing tasks.md.
    544 repo stars
  69. ▌
    Speckit Agent Context Update 2 · opsmill
    Refresh the managed Spec Kit section in coding agent context file(s)
    544 repo stars
  70. ▌
    Speckit Agent Context Update · opsmill
    Refresh the managed Spec Kit section in coding agent context file(s)
    544 repo stars
  71. ▌
    Speckit Opsmill Retrospect · opsmill
    Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.
    544 repo stars
  72. ▌
    Infrahub Analyst · opsmill bundle
    Analyze and correlate Infrahub data using the MCP server. Use when querying live infrastructure data to answer operational questions, detect drift, correlate node types, investigate service impact, check maintenance windows, or produce ad-hoc reports — without writing pipeline code.
    544 repo stars
  73. ▌
    Infrahub Menu Creator · opsmill bundle
    Create and manage Infrahub custom menus. Use when designing navigation menus, organizing node types in the UI, or customizing the Infrahub web interface sidebar.
    544 repo stars
  74. ▌
    Infrahub Repo Auditor · opsmill bundle
    Audit an Infrahub repository against all best practices and rules. Use when reviewing a project for compliance, onboarding to an existing repo, or before deployment to catch issues early.
    544 repo stars
  75. ▌
    Infrahub Check Creator · opsmill bundle
    Create and manage Infrahub check definitions. Use when writing validation logic, creating Python checks that run in proposed change pipelines, or building data quality guards for Infrahub.
    544 repo stars
  76. ▌
    Infrahub Object Creator · opsmill bundle
    Create and manage Infrahub object data files. Use when populating infrastructure data, creating device instances, locations, organizations, module installations, or any other data objects for an Infrahub repository.
    544 repo stars
  77. ▌
    Infrahub Schema Creator · opsmill bundle
    Create, validate, and modify Infrahub schemas. Use when designing data models, creating schema nodes with attributes and relationships, validating schema definitions, or planning schema migrations for Infrahub.
    544 repo stars
  78. ▌
    Infrahub Generator Creator · opsmill bundle
    Create and manage Infrahub Generators. Use when building design-driven automation that creates infrastructure objects from templates, topology definitions, or any design-to-implementation workflow in Infrahub.
    544 repo stars
  79. ▌
    Infrahub Transform Creator · opsmill bundle
    Create and manage Infrahub transforms. Use when building data transformations, config generation, or any workflow that converts Infrahub data into a different format (JSON, text, CSV, device configs) using Python or Jinja2 templates.
    544 repo stars
  80. ▌
    Creating Prd · opsmill
    Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.
    544 repo stars
  81. ▌
    Quality Gates · opsmill bundle
    Shared in-workflow quality gates for code/PR skills — the gate model, trust tiers, and the three primitives (evidence-before-done, independent judge, anti-gaming). DO NOT TRIGGER directly — referenced by consumer skills via relative path.
    544 repo stars
  82. ▌
    Speckit Git Feature · opsmill
    Validate Jira/JPD ticket reference and create a feature branch
    544 repo stars
  83. ▌
    Upgrade Infrahub · opsmill
    Upgrade the Infrahub platform version in this project. Handles downloading the new compose file, upgrading the SDK, updating version references across Dockerfile, docker-compose.override.yml, and .envrc, and rebuilding the Docker image. Use this skill whenever the user asks to upgrade, bump, or update the Infrahub version — even if they just say something like "bump infrahub to 1.9" or "upgrade to latest infrahub" or "update infrahub version".
    544 repo stars
  84. ▌
    Opsmill Dev Pr · opsmill
    Opens a pull request, publishing the current branch as a PR. TRIGGER when: the user wants to open a pull request, publish the current branch as a PR, or take the current work through to an open PR. DO NOT TRIGGER when: only committing changes → opsmill-dev-commit; babysitting CI after the PR is already open → opsmill-dev-monitoring-pull-requests.
    544 repo stars
  85. ▌
    Opsmill Dev Commit · opsmill
    Stages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream. TRIGGER when: the user wants to commit, save, or check in the current changes. DO NOT TRIGGER when: opening a pull request → opsmill-dev-pr.
    544 repo stars
  86. ▌
    Opsmill Dev Rebase · opsmill
    Rebases a feature branch onto its latest base, resolving conflicts while preserving the intent of local changes, optionally force-pushing and watching CI afterward. TRIGGER when: the user wants to rebase a feature branch, update a branch against its base, or replay local work on top of the latest upstream. DO NOT TRIGGER when: merging a release branch into dev → opsmill-dev-merging-branches; only watching CI on an already-open PR → opsmill-dev-monitoring-pull-requests.
    544 repo stars
  87. ▌
    Opsmill Dev Fixing Bugs · opsmill
    Implements and validates the fix for a bug once a failing reproduction test exists. TRIGGER when: a bug has a failing reproduction test and you are ready to make it pass, implementing the root-cause fix, the final step of the bug-fixing pipeline. DO NOT TRIGGER when: no reproduction test exists yet → opsmill-dev-test-driving-bugs; still diagnosing, or asked to fix a bug with no analysis or reproduction test yet → opsmill-dev-analyzing-bugs.
    544 repo stars
  88. ▌
    Opsmill Dev Creating Prd · opsmill
    Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → opsmill-dev-creating-issues; the idea has not been stress-tested yet → opsmill-dev-grilling-ideas first; bug reports.
    544 repo stars
  89. ▌
    Opsmill Dev Analyzing Bugs · opsmill
    Performs root-cause analysis of a bug — from a GitHub issue, an issue URL, or a free-text description — before any reproduction or fix is written. TRIGGER when: triaging or diagnosing a bug, investigating why something misbehaves, an issue number/URL handed over for analysis, needing the root cause before touching code. DO NOT TRIGGER when: a failing reproduction test already exists and you are ready to fix → opsmill-dev-fixing-bugs; writing that reproduction test → opsmill-dev-test-driving-bugs; capturing a new bug as a ticket → opsmill-dev-creating-issues.
    544 repo stars
  90. ▌
    Opsmill Dev Grilling Ideas · opsmill
    Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → opsmill-dev-creating-prd.
    544 repo stars
  91. ▌
    Opsmill Dev Creating Issues · opsmill
    Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → opsmill-dev-creating-prd; the idea is still fuzzy and unhardened → opsmill-dev-grilling-ideas first.
    544 repo stars
  92. ▌
    Opsmill Dev Merging Branches · opsmill
    Merges one long-lived branch into another (e.g. a release branch into the main development branch) on a fresh integration branch, or takes over a stalled merge-conflict PR. TRIGGER when: phrasings like "merge <release> into <dev>", "take over this merge-conflict PR", or a GitHub PR link for a branch sync. DO NOT TRIGGER when: replaying local work onto the latest base → opsmill-dev-rebase; opening a pull request → opsmill-dev-pr.
    544 repo stars
  93. ▌
    Opsmill Dev Pruning Residues · opsmill
    Use when an artifact has been argued, iterated, or debugged into its current shape and now carries rationale that only made sense in the process that produced it. Applies to docs, code comments, commit and PR/issue text, and config-file comments. Sweeps the artifact so it states what it does, not why it was argued into that shape. Triggers on "tidy this", "strip the residue", "make this read standalone".
    544 repo stars
  94. ▌
    Opsmill Dev Backporting Fixes · opsmill
    Ports an existing fix from one long-lived branch to another (e.g. a stable fix landed on the development branch), adapting it to the target branch's current code rather than cherry-picking blindly. TRIGGER when: phrasings like "backport <fix/PR/commit> to <branch>", "port this stable fix to develop", "land <ticket> on <branch> too", or a fix that already exists on one branch has to land on another. DO NOT TRIGGER when: syncing one whole branch into another wholesale → opsmill-dev-merging-branches; replaying local work onto its base → opsmill-dev-rebase; fixing a brand-new bug that has no existing fix → opsmill-dev-analyzing-bugs / opsmill-dev-fixing-bugs.
    544 repo stars
  95. ▌
    Opsmill Dev Test Driving Bugs · opsmill
    Writes a single failing test that reproduces a bug after its root-cause analysis is complete, before any fix is written. TRIGGER when: a bug has a completed root-cause analysis and you need the failing reproduction test, writing a test that proves a bug exists, the second step of the bug-fixing pipeline. DO NOT TRIGGER when: still triaging or diagnosing the bug → opsmill-dev-analyzing-bugs; implementing the fix once the test exists → opsmill-dev-fixing-bugs; general feature test-first work → superpowers test-driven-development.
    544 repo stars
  96. ▌
    Opsmill Dev Monitoring Pull Requests · opsmill
    Watches an open pull request's CI until green and fixes failing checks. TRIGGER when: the user wants to watch a pull request's CI, babysit a PR until it goes green, or fix failing CI checks on an open PR. DO NOT TRIGGER when: opening the PR in the first place → opsmill-dev-pr; rebasing the branch onto its base → opsmill-dev-rebase.
    544 repo stars
  97. ▌
    Opsmill Dev Analyzing Dependency Bumps · opsmill
    Produces a breaking-change / deprecation / opportunity report for a dependency-bump PR, grounded in how this codebase actually uses each bumped package, not the changelog alone. TRIGGER when: the user gives a PR URL or number for a dependency version bump (Dependabot, Renovate, or hand-rolled) and asks what could break, what changed, or whether it is safe to merge (e.g. "scan this dependabot PR", "what breaks if we take this bump", "is <PR url> safe to merge"). DO NOT TRIGGER when: the PR is a feature or bugfix rather than a dependency version bump → a code-review or bug skill instead.
    544 repo stars
  98. ▌
    Infrahub Importing Data · opsmill bundle
    Converts CSV/TSV inputs into Infrahub object YAML and loads them onto a fresh branch. Handles a single file, a folder of files, an explicit list of paths, and one-big-denormalized-sheet exports. TRIGGER when: importing CSV, loading CSV/TSV into Infrahub, ingesting spreadsheet data, converting CSV to Infrahub objects, splitting a denormalized CSV across multiple kinds. DO NOT TRIGGER when: running `infrahubctl import load` against an LDJSON dump (different format and tool), designing or modifying schemas (this skill is read-only against the schema and fails closed on unmapped columns), exporting data from Infrahub (use `infrahubctl object get -o csv` for single-kind export), or ingesting JSON/XLSX (v1 is CSV+TSV only).
    544 repo stars
  99. ▌
    Infrahub Reporting Issues · opsmill bundle
    Reports bugs and feature requests against the right Infrahub-ecosystem GitHub repository. Classifies the request, routes it (with the main `opsmill/infrahub` repo as the safe fallback when in doubt), searches for existing duplicates, gathers conservative environment info for bugs, and prepares the issue for the user to review before any submission. TRIGGER when: user wants to report a bug, file an issue, request a feature, open a ticket, or escalate a problem in any opsmill/infrahub-* project (SDK, Ansible, VS Code, MCP, Helm, schema-library, sync, backup, nornir, skills). DO NOT TRIGGER when: the user wants to fix the bug themselves locally, write a test, or debug code without filing.
    544 repo stars
  100. ▌
    Infrahub Reporting Skill Gaps · opsmill bundle
    Turns friction from an Infrahub skill session into a reviewed GitHub issue about an Infrahub skill's guidance. Infrahub skills fail quietly: a missing or unclear rule does not crash, it produces extra round trips and repeated user nudges. This skill gathers evidence of that friction, checks the tracker for an existing report, works out whether the skill or the underlying product is at fault, and drafts a proposed rule change. It never files anything itself: it hands the redacted draft to infrahub-reporting-issues, which shows it to the user and gets explicit approval before any submission. TRIGGER when: accepting a friction offer, the user says "report skill friction", asks why an Infrahub skill kept failing or needed so many retries, or wants a gap in an Infrahub skill's guidance reported. DO NOT TRIGGER when: reporting a bug in Infrahub itself or any other opsmill/infrahub-* product (use infrahub-reporting-issues instead), or for ordinary Infrahub work where nothing went wrong.
    544 repo stars