all publishers

opsmill

@opsmill source repo

164 published skills · page 2 of 2

  1. ▌
    Infrahub Analyzing Diagnostics · opsmill bundle
    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 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).
    544 repo stars
  2. ▌
    Infrahub Collecting Diagnostics · 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: 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).
    544 repo stars
  3. ▌
    Speckit Review Run · opsmill
    Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.
    544 repo stars
  4. ▌
    Speckit Critique Run · 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
  5. ▌
    Speckit Opsmill Auto · 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
  6. ▌
    Speckit Opsmill Prep · opsmill
    Run the speckit preparation phases end-to-end — specify, plan, critique, tasks — making all decisions autonomously. Stops before implementation.
    544 repo stars
  7. ▌
    Speckit Opsmill Summary · 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
  8. ▌
    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 → commit; babysitting CI after the PR is already open → monitoring-pull-requests.
    544 repo stars
  9. ▌
    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 → pr.
    544 repo stars
  10. ▌
    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 → merging-branches; only watching CI on an already-open PR → monitoring-pull-requests.
    544 repo stars
  11. ▌
    Feature Flow · opsmill
    Multi-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.
    544 repo stars
  12. ▌
    Audit Docs · opsmill
    Audits 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`.
    544 repo stars
  13. ▌
    Capture Knowledge · opsmill
    Capture 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.
    544 repo stars
  14. ▌
    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 → creating-prd.
    544 repo stars
  15. ▌
    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 → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.
    544 repo stars
  16. ▌
    Harvesting Review · opsmill
    Mines 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.
    544 repo stars
  17. ▌
    Neo4j Cypher Guide · opsmill bundle
    Comprehensive 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.
    544 repo stars
  18. ▌
    Migrate Feature Page · opsmill
    Migrate 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.
    544 repo stars
  19. ▌
    Analyzing CI Flakiness · opsmill bundle
    Analyzes 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.
    544 repo stars
  20. ▌
    Speckit Opsmill Extract · opsmill
    Extract knowledge, guidelines, and ADRs from one or more completed spec directories into the project documentation system.
    544 repo stars
  21. ▌
    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 → pr; rebasing the branch onto its base → rebase.
    544 repo stars
  22. ▌
    Creating Changelog Entries · opsmill
    Use 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.
    544 repo stars
  23. ▌
    Speckit Opsmill Implement · 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
  24. ▌
    Speckit Review · opsmill
    Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.
    544 repo stars
  25. ▌
    Speckit Archive · opsmill
    Archive a feature specification into main project memory after merge, resolving gaps and conflicts
    544 repo stars
  26. ▌
    Speckit Auto Run · opsmill
    Run the full speckit workflow end-to-end — specify, plan, critique, tasks, implement, review, extract — making all decisions autonomously.
    544 repo stars
  27. ▌
    Speckit Extract Run · opsmill
    Extract knowledge, guidelines, and ADRs from one or more completed spec directories into the project documentation system.
    544 repo stars
  28. ▌
    Speckit Review Code · opsmill
    General code quality review — project guideline compliance, bug detection, code quality analysis.
    544 repo stars
  29. ▌
    Speckit Summary Run · 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
  30. ▌
    Speckit Review Tests · opsmill
    Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.
    544 repo stars
  31. ▌
    Speckit Review Types · opsmill
    Type design analysis — encapsulation, invariant expression, usefulness, and enforcement.
    544 repo stars
  32. ▌
    Speckit Iterate Apply · opsmill
    Apply a pending iteration to spec documents — update all artifacts that speckit.implement relies on, then hand off to implementation.
    544 repo stars
  33. ▌
    Speckit Reconcile Run · opsmill
    Reconcile implementation drift by updating the feature's own spec, plan, and tasks
    544 repo stars
  34. ▌
    Speckit Review Errors · opsmill
    Error handling review — silent failure detection, catch block analysis, error logging.
    544 repo stars
  35. ▌
    Speckit Iterate Define · opsmill
    Define an iteration on the current feature — analyze the change request against current spec state and implementation progress, then write a reviewable iteration plan.
    544 repo stars
  36. ▌
    Speckit Retrospect Run · opsmill
    Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.
    544 repo stars
  37. ▌
    Speckit Review Comments · opsmill
    Code comment accuracy verification, documentation completeness assessment, comment rot detection.
    544 repo stars
  38. ▌
    Speckit Review Simplify · opsmill
    Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.
    544 repo stars
  39. ▌
    Speckit Checkpoint Commit · opsmill
    Commit changes at meaningful checkpoints throughout the workflow
    544 repo stars
  40. ▌
    Speckit Tinyspec Classify · opsmill
    Classify task complexity and recommend tinyspec or full SDD workflow
    544 repo stars
  41. ▌
    Speckit Tinyspec Tinyspec · opsmill
    Generate a single lightweight spec file with context, plan, and tasks for small changes
    544 repo stars
  42. ▌
    Speckit Tinyspec Implement · opsmill
    Implement a small change directly from its tinyspec file
    544 repo stars
  43. ▌
    Speckit Plan · opsmill
    Execute the implementation planning workflow using the plan template to generate design artifacts.
    544 repo stars
  44. ▌
    Speckit Tasks · opsmill
    Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
    544 repo stars
  45. ▌
    Infrahub Common · 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
  46. ▌
    Speckit Analyze · 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
  47. ▌
    Speckit Clarify · 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
  48. ▌
    Speckit Specify · opsmill
    Create or update the feature specification from a natural language feature description.
    544 repo stars
  49. ▌
    Speckit Converge · 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
  50. ▌
    Speckit Checklist · opsmill
    Generate a custom checklist for the current feature based on user requirements.
    544 repo stars
  51. ▌
    Speckit Implement · opsmill
    Speckit Implement
    544 repo stars
  52. ▌
    Speckit Constitution · opsmill
    Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
    544 repo stars
  53. ▌
    Speckit Taskstoissues · opsmill
    Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
    544 repo stars
  54. ▌
    Infrahub Auditing Repo · 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
  55. ▌
    Infrahub Analyzing Data · 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.
    544 repo stars
  56. ▌
    Infrahub Managing Menus · 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
  57. ▌
    Infrahub Managing Checks · opsmill bundle
    Creates 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.
    544 repo stars
  58. ▌
    Infrahub Managing Objects · 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
  59. ▌
    Infrahub Managing Schemas · 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. DO NOT TRIGGER when: populating data objects, writing checks/generators/transforms, querying live data.
    544 repo stars
  60. ▌
    Infrahub Managing Generators · 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
  61. ▌
    Infrahub Managing Transforms · opsmill bundle
    Creates 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.
    544 repo stars
  62. ▌
    Speckit Infrahub Speckit Route Plan · 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
  63. ▌
    Speckit Infrahub Speckit Route Specify · 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
  64. ▌
    Speckit Infrahub Speckit Route Implement · 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