rook-release: Skill for Claude Code

Clean Layers

Compare the currently open Rhino file's layer structure against the project's .rook/conventions.yaml and propose targeted changes to bring it into compliance. Never makes changes without user approval.

This is the execution side of the convention system. /capture-convention captures the policy; this skill enforces it.

Prerequisites

• A Rhino file must be open
• A .rook/conventions.yaml must exist in the project directory (created by /capture-convention or written by hand)
• Rook MCP tools must be available (rhino_ping returns pong)

If no conventions.yaml exists, tell the user: "No convention file found. Run /capture-convention first to define your layer standards, or place a .rook/conventions.yaml in your project directory."

Workflow

Step 0: Preflight

1. Call rhino_ping. If no response, stop.

2. Call rhino_document to get the file name and path.

3. Look for .rook/conventions.yaml relative to the file's directory. If the file is at C:\Projects\MyProject\model.3dm, check C:\Projects\MyProject\.rook\conventions.yaml. Also check the current working directory.

4. Read and parse the conventions.yaml. If it fails to parse, report the error and stop.

5. Offer to create a backup copy. Layer cleanup is a multi-step operation and Ctrl+Z may not cleanly revert everything. Offer: "Before making changes, I can save a backup copy of {filename} as {filename_without_ext}_BACKUP.3dm in the same directory. If anything goes wrong, you can delete the modified file and rename the backup. Create a backup? (recommended)"

   If the user accepts, use rhino_command or rhino_execute to SaveAs to the backup path, then SaveAs back to the original path so the working file stays at its original location. Or simply copy the .3dm file on disk before any Rhino mutations begin.

   If the user declines, proceed without backup — their choice.

6. Tell the user: "I'll compare {filename} against the {convention name} convention. This is an audit — no changes until you approve."