rook-release: Skill for Claude Code

Execute Grasshopper Work

Authorization

A direct build or edit request authorizes the bounded mutations needed to produce the requested result. Ask again only when the request is ambiguous, destructive, would change pre-existing content outside the admitted boundary, or would materially expand scope.

Execution owns mutation. It may consume a clear brief, an approved design, or an optional technical plan.

Admit the Live Target

Before mutation:

1. Confirm the intended host and document identity.
2. Capture a fresh gh_snapshot and take its fresh epoch for the immediate batch.
3. Resolve every unfamiliar component identity with gh_library and every required port with gh_batch_component_info.
4. When a needed admitted tool is hidden, use rook_tools_search, rook_tools_read, and rook_tools_call.
5. Compare any optional structural baseline with the live document.
6. Start an execution-owned ID ledger containing temporary IDs, committed IDs, authorized pre-existing IDs, and operation outcomes.

For Wasp work, apply ../design-grasshopper/references/wasp-admission.md. Failed admission stops before mutation with the missing component or port evidence reported.

If no admitted host, mutation tool, or required live component can be reached, stop without mutation. Preserve useful design or plan artifacts and report the unavailable boundary.

Admit Drift

Refresh volatile component identities and ports when their meaning is unchanged. Omit operations already satisfied by the live graph.

Stop for approval when drift changes semantics, topology, ownership, or preservation obligations. A missing or stale structural baseline is advisory only; re-admit the live state before acting.

Apply Bounded Batches

Use gh_edit for ordered batch mutation. It may return partial_success: earlier operations may commit before a later operation fails.

Route component authoring by capability:

• create ordinary Grasshopper components through gh_edit;
• create modern Python or C# script components through gh_create_script (or its language-specific alias); and
• create Chirp components through chirp_create; and
• correct existing script source or pins through gh_update_script and gh_set_script_pins.