workflow-review-changes

[BLOCKING] Execute skill steps in declared order. NEVER skip, reorder, or merge steps without explicit user approval. [BLOCKING] Before each step or sub-skill call, update task tracking: set in_progress when step starts, set completed when step ends. [BLOCKING] Every completed/skipped step MUST include brief evidence or explicit skip reason. [BLOCKING] If Task tools are unavailable, create and maintain an equivalent step-by-step plan tracker with the same status transitions.

IMPORTANT MANDATORY Steps: /review-changes -> [parallel batch] /review-architecture + /review-domain-entities (if entity changes) + /performance + /integration-test-review + /security -> /code-simplifier -> /code-review -> /integration-test-verify -> /plan -> /plan-validate -> /why-review -> /cook -> fresh sub-agent re-review gate -> /docs-update -> /watzup -> /workflow-end

[WORKFLOW-IN-WORKFLOW: MUST RUN AS SUB-AGENT when inside another workflow] This skill activates the full review-changes workflow (16 steps). When invoked as a step inside a parent workflow (e.g., feature, bugfix, refactor), it MUST execute via Agent tool (subagent_type: "code-reviewer") — NEVER as an inline Skill tool call. Inline execution absorbs 16 steps of context into the parent session.

Sub-agent prompt must include: current git diff, feature/task description, instruction to return SYNC:subagent-return-contract summary and write full findings to plans/reports/.

Standalone invocation (not inside a workflow): inline execution is fine — no sub-agent required.

[BLOCKING] Each step MUST ATTENTION invoke its Skill tool — marking a task completed without skill invocation is a workflow violation. NEVER batch-complete validation gates. [FRESH SUB-AGENT RE-REVIEW] After fixes in /cook, spawn a fresh sub-agent per SYNC:fresh-context-review for unbiased re-review. Max 3 fresh rounds per conversation.