grounding-rules

Ship a new version of THIS repo's grounding-rules skill in one step — publish (bump + changelog + commit + tag + push via scripts/publish.sh) then refresh the local plugin install (`claude plugin marketplace update grounding-rules`). Use when the user types /release in the grounding-rules repo, or asks to release / publish / cut a new grounding-rules version. Maintainer-only — this project skill is not shipped to plugin consumers.

Distill a system or subsystem into a short, human-readable set of GROUNDING RULES — the minimal load-bearing invariants and design decisions that let a reader gain CONFIDENCE in the system in minutes and adjudicate future design choices, instead of reading a full spec for hours. Use this whenever the user wants the "essence" / "constitution" of a module, the load-bearing rules / single-source-of-truth / key invariants of a system, a first-principles explanation of how a subsystem really works (not API-reference docs), or types /grounding-rules. Three actions: a fresh grounding pass; `update <new facts or corrections>` (re-ground an existing doc when the system changes); and `ask <question>` (answer from the real code in the grounding voice). Favors compression and the good-faith reader: only rules that matter, that can't be inferred from the others, and whose plain reading makes the right choice the obvious one. Writes to a vault path → invokes obsidian-markdown. NOT for exhaustive API reference, tutorials, c