opsmill
- 164 skills
- 0 followers
- 544 repo stars
- last month last updated
- ▌ Infrahub Analyzing Diagnostics · opsmill bundleAnalyze 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 TRIGGER when: no bundle exists yet — collect one first (use infrahub-collecting-diagnostics), filing the issue itself (use infrahub-reporting-issues), or querying live data (use infrahub-analyzing-data).
- ▌ Infrahub Collecting Diagnostics · opsmill bundleCollect 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: a bundle has already been collected and the user wants it analyzed (use infrahub-analyzing-diagnostics), filing a public GitHub issue (use infrahub-reporting-issues), or running operational queries (use infrahub-analyzing-data).
- ▌ Speckit Review Run · opsmillComprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.
- ▌ Speckit Critique Run · opsmillPerform a dual-lens critical review of the specification and plan from both product strategy and engineering risk perspectives before implementation.
- ▌ Speckit Opsmill Auto · opsmillRun the full speckit workflow end-to-end — specify, plan, critique, tasks, implement, review — making all decisions autonomously. Stops before extract; run that manually.
- ▌ Speckit Opsmill Prep · opsmillRun the speckit preparation phases end-to-end — specify, plan, critique, tasks — making all decisions autonomously. Stops before implementation.
- ▌ Speckit Opsmill Summary · opsmillProduce 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.
- ▌ Pr · opsmillOpens 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.
- ▌ Commit · opsmillStages 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.
- ▌ Rebase · opsmillRebases 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.
- ▌ Feature Flow · opsmillMulti-phase orchestrator for a feature: spec → plan → implement → review → CI gate → PR. Uses parallel agents for divergent thinking and a single synthesizer between phases. Trigger when the user says 'start the feature flow', 'run feature-flow', or names a ticket and asks to drive it end to end.
- ▌ Audit Docs · opsmillAudits internal (dev/) and external (docs/) documentation completeness for a feature, subject, or set of existing docs, maps changes indicated by the user, across Infrahub's documentation layers, reports gaps, and optionally applies the fixes. TRIGGER when: the user wants to audit or check documentation coverage, find doc gaps after a feature branch, or verify docs are still current for a subject or specific files. DO NOT TRIGGER when: authoring new documentation from scratch → use the add-docs flow; only linting/formatting Markdown → run `uv run invoke docs.lint`.
- ▌ Capture Knowledge · opsmillCapture non-obvious facts learned while working into dev/knowledge/, dev/guidelines/, or dev/guides/ so future agents understand the code faster. Trigger when the user says 'capture this', 'document this', 'we should write that down', or autonomously at the end of a feature when something non-obvious was learned.
- ▌ Grilling Ideas · opsmillStress-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.
- ▌ Creating Issues · opsmillTurns 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.
- ▌ Harvesting Review · opsmillMines a pull request's review threads for lessons that generalize beyond that PR, reconstructs each against the actual code before deciding, checks whether it is already codified, and routes the genuinely-new, durable ones into Infrahub's internal documentation — `dev/knowledge/`, `dev/guides/`, `dev/guidelines/`, the `AGENTS.md` files, and `.agents/rules/` — proposing edits first and applying only with the user's approval. TRIGGER when: the user wants to turn PR review feedback into durable conventions, guidelines, or rules; capture recurring reviewer comments as internal documentation; or check whether review lessons are reflected in the knowledge/guides/guidelines/AGENTS.md/rules layer. DO NOT TRIGGER when: sweeping a feature's changes for documentation coverage across all layers → use `audit-docs`; extracting knowledge from completed spec directories → `speckit-opsmill-extract`; only replying to or resolving review threads → normal git/gh flow.
- ▌ Neo4j Cypher Guide · opsmill bundleComprehensive guide for writing modern Neo4j Cypher queries. Essential for text2cypher MCP tools and LLMs generating Cypher queries. Covers removed/deprecated syntax, modern replacements, CALL subqueries for reads, COLLECT patterns, sorting best practices, set-based writes, and Quantified Path Patterns (QPP) for efficient graph traversal.
- ▌ Migrate Feature Page · opsmillMigrate Infrahub docs feature pages from the legacy topic+guide pair into a cleaner structure (single merged page, hub+spokes, or tutorial extraction). Supports both single-feature migrations (one feature like Profiles or Webhooks) and section-wide migrations (a whole section like Branches & Change Control with multiple features migrated together) when the team has agreed on a section-wide restructure plan. Trigger when the user names a specific feature or section to migrate (e.g. "let's migrate profiles", "start the Resource Manager migration", "do the entire Branches & Change Control section"). Each migration is its own branch off `demo/groups-diataxis-example`, its own PR back to that branch.
- ▌ Analyzing CI Flakiness · opsmill bundleAnalyzes recent CI failures on pull requests to identify flaky tests, using retry outcomes (failed attempt → green re-run) and cross-PR recurrence as evidence, and maintains a local longitudinal ledger so flakiness can be tracked over time. TRIGGER when: the user wants to find flaky tests, correlate recent CI failures, check which tests fail across PRs or recover on retry, or refresh the flakiness trend report. DO NOT TRIGGER when: babysitting a single PR's CI until green → monitoring-pull-requests; diagnosing or fixing one specific failing test → the bug-analysis skills.
- ▌ Speckit Opsmill Extract · opsmillExtract knowledge, guidelines, and ADRs from one or more completed spec directories into the project documentation system.
- ▌ Monitoring Pull Requests · opsmillWatches 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.
- ▌ Creating Changelog Entries · opsmillUse when you've fixed a bug, added a feature, or made any user-facing change in a project that uses Towncrier and need to record it for the changelog — before committing or opening a PR, or whenever asked to add a changelog entry, towncrier fragment, or news fragment.
- ▌ Speckit Opsmill Implement · opsmillRun 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.
- ▌ Speckit Review · opsmillComprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.
- ▌ Speckit Archive · opsmillArchive a feature specification into main project memory after merge, resolving gaps and conflicts
- ▌ Speckit Auto Run · opsmillRun the full speckit workflow end-to-end — specify, plan, critique, tasks, implement, review, extract — making all decisions autonomously.
- ▌ Speckit Extract Run · opsmillExtract knowledge, guidelines, and ADRs from one or more completed spec directories into the project documentation system.
- ▌ Speckit Review Code · opsmillGeneral code quality review — project guideline compliance, bug detection, code quality analysis.
- ▌ Speckit Summary Run · opsmillProduce 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.
- ▌ Speckit Review Tests · opsmillTest coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.
- ▌ Speckit Review Types · opsmillType design analysis — encapsulation, invariant expression, usefulness, and enforcement.
- ▌ Speckit Iterate Apply · opsmillApply a pending iteration to spec documents — update all artifacts that speckit.implement relies on, then hand off to implementation.
- ▌ Speckit Reconcile Run · opsmillReconcile implementation drift by updating the feature's own spec, plan, and tasks
- ▌ Speckit Review Errors · opsmillError handling review — silent failure detection, catch block analysis, error logging.
- ▌ Speckit Iterate Define · opsmillDefine an iteration on the current feature — analyze the change request against current spec state and implementation progress, then write a reviewable iteration plan.
- ▌ Speckit Retrospect Run · opsmillRun a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.
- ▌ Speckit Review Comments · opsmillCode comment accuracy verification, documentation completeness assessment, comment rot detection.
- ▌ Speckit Review Simplify · opsmillCode simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.
- ▌ Speckit Checkpoint Commit · opsmillCommit changes at meaningful checkpoints throughout the workflow
- ▌ Speckit Tinyspec Classify · opsmillClassify task complexity and recommend tinyspec or full SDD workflow
- ▌ Speckit Tinyspec Tinyspec · opsmillGenerate a single lightweight spec file with context, plan, and tasks for small changes
- ▌
- ▌ Speckit Plan · opsmillExecute the implementation planning workflow using the plan template to generate design artifacts.
- ▌ Speckit Tasks · opsmillGenerate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
- ▌ Infrahub Common · opsmill bundleShared 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.
- ▌ Speckit Analyze · opsmillPerform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
- ▌ Speckit Clarify · opsmillIdentify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
- ▌ Speckit Specify · opsmillCreate or update the feature specification from a natural language feature description.
- ▌ Speckit Converge · opsmillAssess 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.
- ▌ Speckit Checklist · opsmillGenerate a custom checklist for the current feature based on user requirements.
- ▌
- ▌ Speckit Constitution · opsmillCreate or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
- ▌ Speckit Taskstoissues · opsmillConvert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
- ▌ Infrahub Auditing Repo · opsmill bundleAudits 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.
- ▌ Infrahub Analyzing Data · opsmill bundleAnalyzes 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.
- ▌ Infrahub Managing Menus · opsmill bundleCreates 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.
- ▌ Infrahub Managing Checks · opsmill bundleCreates Infrahub check definitions — Python validation logic and GraphQL queries for proposed change pipelines. TRIGGER when: writing validation checks, creating Python checks, building data quality guards for proposed changes. DO NOT TRIGGER when: designing schemas, querying live data, building transforms or generators.
- ▌ Infrahub Managing Objects · opsmill bundleCreates 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.
- ▌ Infrahub Managing Schemas · opsmill bundleCreates, 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. DO NOT TRIGGER when: populating data objects, writing checks/generators/transforms, querying live data.
- ▌ Infrahub Managing Generators · opsmill bundleCreates 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.
- ▌ Infrahub Managing Transforms · opsmill bundleCreates Infrahub transforms that convert data into JSON, text, CSV, or device configs using Python or Jinja2 templates. TRIGGER when: building config generation, data export, format conversion, Jinja2 templates, artifact pipelines. DO NOT TRIGGER when: designing schemas, writing validation checks, creating generators, querying live data.
- ▌ Speckit Infrahub Speckit Route Plan · opsmillHook 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.
- ▌ Speckit Infrahub Speckit Route Specify · opsmillHook 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.
- ▌ Speckit Infrahub Speckit Route Implement · opsmillHook 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.