opsmill

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Perform a dual-lens critical review of the specification and plan from both product strategy and engineering risk perspectives before implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Code comment accuracy verification, documentation completeness assessment, comment rot detection.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Refresh the managed Spec Kit section in coding agent context file(s)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Auto-commit changes after a Spec Kit command completes

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validate Jira/JPD ticket reference and create a feature branch

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Detect Git remote URL for GitHub integration

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validate current branch follows feature branch naming conventions

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Execute the implementation plan by processing and executing all tasks defined in tasks.md

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Extract knowledge, guidelines, and ADRs from one or more completed spec directories into the project documentation system.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.