OpsMill
Official@opsmill
Infrahub by OpsMill
Agent Skills by OpsMill
Showing 55 vetted skills indexed across 2 GitHub repositories.
opsmillspeckit-opsmill-retrospect
Runs a session retrospective that classifies context-management gaps into approved follow-up actions.
opsmillinfrahub-managing-generators
Creates Infrahub Generators that build infrastructure objects from design definitions and GraphQL queries.
opsmillinfrahub-reporting-issues
Routes and drafts bug reports and feature requests for Infrahub-ecosystem GitHub repositories.
opsmillspeckit-converge
Assess codebase against spec, plan, and tasks, then append remaining work to tasks.md.
opsmillinfrahub-managing-transforms
Creates Infrahub transforms converting GraphQL data into JSON, CSV, or device configs via Python or Jinja2.
opsmillinfrahub-importing-data
Converts CSV and TSV files into Infrahub object YAML and loads them onto a review branch.
opsmillspeckit-opsmill-implement
Executes speckit tasks.md implementation in clean-context subagents with review and reporting.
opsmillinfrahub-managing-objects
Creates and validates Infrahub object YAML files for populating infrastructure data.
opsmillinfrahub-analyzing-data
Queries and correlates live Infrahub infrastructure data via the MCP server to answer operational questions.
opsmillinfrahub-managing-menus
Creates Infrahub custom navigation menus organizing schema node types into sidebar hierarchies.
opsmillspeckit-opsmill-auto
Orchestrates the full speckit workflow from specification through implementation autonomously.
opsmillinfrahub-managing-schemas
Creates, validates, and modifies Infrahub schema YAML files defining nodes, generics, attributes, and relationships.
opsmillinfrahub-auditing-repo
Audits Infrahub repositories against schema, object, and Python rules to produce a compliance report.
opsmillspeckit-opsmill-prep
Runs speckit specify, plan, critique, and tasks phases autonomously before implementation.
opsmillupgrade-infrahub
Upgrades the Infrahub platform version across compose files, SDK, Dockerfile, and Docker images.
opsmillinfrahub-collecting-diagnostics
Collects redacted Infrahub logs, config, and state into a diagnostic bundle for support hand-off.
opsmillspeckit-opsmill-summary
Generates a flow-level markdown summary of the current Claude Code session into the feature directory.
opsmillspeckit-opsmill-extract
Extracts ADRs, knowledge, and guidelines from completed spec directories into project documentation.
opsmillinfrahub-managing-checks
Creates Infrahub check definitions with Python validation logic, GraphQL queries, and YAML-driven tests.
opsmillinfrahub-common
Provides shared GraphQL, configuration, and workflow references for Infrahub automation skills.
opsmillspeckit-checklist
Generate requirements-quality checklists for spec-kit feature specifications.
opsmillspeckit-critique-run
Analyze spec.md and plan.md to produce a structured critique report.
opsmillspeckit-archive
Archive merged feature specifications into main project memory with changelog entries.
opsmillspeckit-review-errors
Audit error handling across code paths and produce a structured report.
Frequently Asked Questions About OpsMill
FAQPage SchemaWhat specific tasks can I perform using OpsMill?▼
OpsMill enables the generation of dependency-ordered task lists, automated extraction of architectural decision records, and structured auditing of code quality. It facilitates the transition from natural language requirements to testable specifications and ensures synchronization between project documentation and repository commits.
Who is the target persona for these capabilities?▼
The primary users are software engineers, technical leads, and architects who manage complex codebases requiring strict adherence to design specifications. It is designed for teams prioritizing test-first development, rigorous documentation standards, and consistent version control practices across distributed development environments.
What are the prerequisites for implementing these specifications?▼
Implementation requires a repository structured around the Spec Kit format, specifically utilizing markdown files such as spec.md, plan.md, and tasks.md. Users must have a configured Git environment to allow the system to validate branch naming conventions and manage commit hooks effectively.