review

A human approval gate blocks automated workflow execution until a developer provides explicit approval. This skill generates a review checklist that enforces this gatekeeping by preventing implementation steps from running until the Overall Decision is OK.

A developer review checklist is a human gate document that tracks implementation requirements and prevents automated execution skills from running until manually approved. It ensures changes tracked under output specs receive explicit human review before proceeding.

To generate a review checklist for morkit changes, run the tool to automatically derive the target change directory and write review-checklist.md. It reads from the Mor Developer Review Checklist and supports variant selection and refresh options.

Yes, you can refresh an existing review checklist using the refresh option. This updates the review-checklist.md file while maintaining the human-gate process that requires explicit approval before subsequent execution steps proceed.

No, the human gate review process strictly enforces guardrails that prevent auto-approval. It requires explicit human approval for the Overall Decision before permitting any implementation or execution skills to run.

If no target change directory is provided, the tool automatically derives it from the morkit changes being tracked. This allows the review checklist generation to proceed without manual directory specification.