peterzat

Fix BLOCK and WARN findings from CODEREVIEW.md. Reads findings as a spec, applies minimal targeted fixes. Never evaluates its own work; that is the reviewer's job. Invoked by /codereview, not directly by users.

Strategic architecture review from the perspective of a Senior Architecture Review Board. Manual invocation only via /architect — do not invoke this skill automatically. Use when the user explicitly asks for an architecture review, design assessment, technology selection review, or strategic technical direction evaluation. Supports focused deep-dives: /architect deps, /architect ops, /architect <t

Test strategy review and design from the perspective of a Principal SDE/T. `/tester` audits the current test strategy and appends a dated finding to TESTING.md. `/tester design` writes (or revises) a durable test-architecture contract in TESTING.md and seeds rollout items in BACKLOG.md. Manual invocation only. Do not invoke automatically.

Adversarial code review of uncommitted or staged changes. Includes a security scan via /security for full-tier reviews (skipped for docs-only changes). Use when the user asks to review code, check changes before pushing, or run a code review. Also use automatically before any git push, unless the user has explicitly said "push now" (unprompted); in that case run `codereview-skip && git push` witho

Create, inspect, or merge GitHub pull requests. Use when the user asks to open a PR, check PR status, or merge a PR. Composes PR descriptions from existing review file metadata. Manual invocation only via /pr.

Generate or evolve a specification (SPEC.md) that defines what done looks like for a unit of work. Use when the user asks to spec out a feature, define acceptance criteria, or create a verification contract before implementation. Manual invocation only via /spec.

Security-focused review from the perspective of a Principal Security Engineer. Use when the user asks for a security review, vulnerability check, or secret scan. Accepts optional scope argument: "changes-only" for proposed changes only, a file path to review specific files, or no argument for a full repository audit.