windsorcli

Inspect the local Windsor cluster health and Flux tuning — kustomizations, helm releases, sources, pods, recent events, suspended/stalled resources, reconciliation intervals, and controller resource usage.

Pre-push review for Windsor Core. Runs parallel passes over staged changes to catch bugs in facets, kustomize, Terraform, and schema before the branch hits CI.

Author Windsor facets, config expressions, and schema additions. Knows facet YAML structure, expression syntax, the layering system (provider > option > addon), and how to write matching test cases.

Push the current branch and open or update its pull request with a Conventional-Commits title. Does NOT author a PR description -- the claude-code-review workflow upserts the canonical summary into the body on every push, so this skill leaves the body empty for CI to fill and never touches an existing one. Run after committing and before announcing the PR. Use whenever the user asks to "open the PR", "push and PR", or after the project's gates are green and the branch is ready.

Author and maintain reference Markdown for the core Windsor blueprint for ingestion into windsorcli.github.io. Use when writing docs under docs/, Terraform module reference, Kustomize stack operator guides (README per stack), or compatibility matrices.

Walk through review comments and failed CI checks on the current branch's PR, propose a fix per finding, and stage it for the author to review BEFORE committing. One pause-and-review cycle per finding. Use when the user says "address PR feedback", "fix the PR comments", "go through the review", or after a `gh pr checks` shows failures and the author wants to work through them one at a time. Pairs with create-pr (outgoing) and review-pr (pre-commit).

Author kustomize components, patches, and overlays using Windsor Core conventions. Knows base/resources/components layering, HelmRelease patterns, patch types, and timeout/interval rules.

Enforce Windsor Core Terraform module structure, naming, and style conventions. Use when creating or editing any Terraform file.

Push the current branch and open or update its pull request with a Conventional-Commits title. Does NOT author a PR description -- the claude-code-review workflow upserts the canonical summary into the body on every push, so this skill leaves the body empty (except for a Closes

Walk through review comments and failed CI checks on the current branch's PR, propose a fix per finding, and stage it for the author to review BEFORE committing. One pause-and-review cycle per finding. Use when the user says "address PR feedback", "fix the PR comments", "go through the review", or after a `gh pr checks` shows failures and the author wants to work through them one at a time. Pairs with create-pr (outgoing) and review-pr (pre-commit).

Enforce Windsor CLI architecture boundaries and separation of concerns. Use when changes touch more than one layer (cmd, runtime, evaluator, secrets, provisioner, composer, workstation), or when ownership of logic is unclear.

Pre-commit bug review. Analyzes the staged diff across multiple parallel passes to find logic bugs, silent failures, security issues, and architecture violations before committing. Run this as the final step before git commit.

Apply Windsor test workflow and design standards for unit tests. Use when writing, expanding, or refactoring tests, or deciding between public boundary coverage vs private method testing.

Enforce Windsor Go file organization, documentation, and package structure conventions. Use when creating or editing any Go implementation, test, mock, or shim file.

Write integration tests that verify CLI command and flag behavior end-to-end. Use when adding new commands, subcommands, or flags, or when expanding coverage in the integration/ directory.

Structure large cross-cutting changes into coherent phases with explicit dependency mapping and test checkpoints. Use when a feature touches multiple runtime subsystems or would otherwise produce an unreviewable single commit.

Walk through review comments and failed CI checks on the current branch's PR, propose a fix per finding, and stage it for the author to review BEFORE committing. One pause-and-review cycle per finding. Use when the user says "address PR feedback", "fix the PR comments", "go through the review", or after a `gh pr checks` shows failures and the author wants to work through them one at a time. Pairs with create-pr (outgoing) and review-pr (pre-commit).

Push the current branch and open or update its pull request with a calm, prose-first description that matches the project's claude-code-review.yaml style. Generates the description ONLY when the PR has no body (or just whitespace) -- a substantial human- or AI-authored body is preserved untouched. Run after committing and before announcing the PR. Use whenever the user asks to "open the PR", "push and PR", or after `task lint && test:unit && test:pester` are green and the branch is ready.

Author and maintain the embedded PowerShell scripts under internal/scripts/. Use when editing any *.ps1 file or the common preamble. Knows the §5 contract this provider locks in — Windows PowerShell 5.1 syntax floor, also tested on 7.4; -EncodedCommand for script body; UTF-8 stdout pin; $ProgressPreference suppression; structured JSON error envelope; ConvertTo-Json -Depth 10 -Compress; CIM cmdlets not WMI; ToString('o') for DateTime. These rules came from spikes

Author terraform-provider-hyperv resources, data sources, the typed Hyper-V client, and connection backends. Use when editing files under internal/provider, internal/resources, internal/datasources, internal/hyperv, internal/connection, internal/types, or when changing schema, plan modifiers, validators, or provider configuration. Knows the terraform-plugin-framework idioms this repo locks in (PLAN.md §8, §11), how MarkdownDescription drives Registry docs (§15), and the SDKv2 anti-patterns to avoid (§11). Not for PowerShell scripts (use powershell-scripter), tests (use test-engineer), or release plumbing.

Write and structure tests across the three tiers this provider uses — Pester (PowerShell scripts standalone), Go unit (with fakeRunner returning canned JSON), and acceptance (TF_ACC=1 against real Hyper-V using terraform-plugin-testing). Use when adding tests for any new resource or data source, expanding coverage, fixing flaky tests, or deciding which tier a given assertion belongs in. Knows the TDD ordering this repo enforces — Pester first to lock the JSON contract, then Go unit, then resource schema, then acceptance, then implementation. Knows the modern terraform-plugin-testing API (statecheck, knownvalue, tfjsonpath, plancheck) and why we don't use the legacy ComposeAggregateTestCheckFunc style.

Pre-commit bug review for terraform-provider-hyperv. Analyzes the staged diff across five parallel passes to find logic bugs, framework anti-patterns, schema-migration risks, sensitive-attribute leaks, PowerShell portability traps, and drift-handling errors before committing. Run as the final step before git commit. Adapted from the windsorcli/cli review-pr skill but tuned for terraform-plugin-framework + Hyper-V/PowerShell concerns. Do not flag style issues, missing comments, or refactoring suggestions — those are handled by other skills (provider-author, powershell-scripter, test-engineer).

Apply Windsor's docs writing style — voice, frontmatter, link conventions, structure, mermaid usage. Use before writing or editing any markdown in this repo.

Pre-PR pass over a docs page or diff. Checks frontmatter, links, terminology, voice, and runs the same linters CI runs. Use before opening a PR.

Run real windsor commands against the docs to confirm they're accurate. Designs efficient validation cycles that stack multiple assertions inside a single init→up→down lifecycle.

Investigate the windsorcli/cli and windsorcli/core repos before writing or revising docs about an evolving feature. Tells you what the code actually does, when it changed, and what's in flight.

Scaffold a new Talos system extension in this repo from `extensions/_template/`. Walks through naming, copying the template into `contrib/<name>/`, filling in `manifest.yaml` + `pkg.yaml`, wiring the target into `.kres.yaml`, regenerating the Makefile with `make rekres`, updating the README catalog, and verifying the build. Use when the user says "add an extension", "scaffold a new extension", "create a new Talos extension", or names a tool they want packaged (e.g. "add fio").

Walk through review comments and failed CI checks on the current branch's PR, propose a fix per finding, and stage it for the author to review BEFORE committing. One pause-and-review cycle per finding. Use when the user says "address PR feedback", "fix the PR comments", "go through the review", or after a `gh pr checks` shows failures and the author wants to work through them one at a time.

Pre-merge review of an open PR on windsorcli/talos-extensions. Reads the full PR diff, the PR description, and CI status, then runs parallel passes covering extension hygiene, build/release impact, supply-chain integrity, schema/lint sanity, and release-notes alignment. Produces a structured Block / Cautions / Clean verdict so the reviewer knows whether to click Merge. Use when the author says "review the PR", "is this ready to merge?", "merge-gate this PR", or after CI goes green and someone needs final eyes. Pairs with `address-pr-feedback` (the author working through review comments) — `review-pr` is the reviewer's side.