cli

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.