You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
proviso show <query> shows the elements an identifier or name
stands for, as you meet it in the tree: an identifier, a term or one
of its aliases, or a contract element or parameter as a rule writes it
in backticks. Each element comes with its text and a frontmatter
naming its type, file, line and the element it belongs to; --json
writes the same as JSON, and --in <capability> narrows the lookup to
one capability and the system level. It reads the tree even where
lint finds errors, so it works in the middle of an amendment.
The skill proviso-explain answers questions about your system
from its spec tree, such as "What does spec tree mean?" or "What
happens when …?", looking every element up with proviso show and
naming where each answer stands. It edits nothing. proviso init
installs it in new repositories; run proviso update to add it to an
existing one.
proviso rehome lists the mentions of every identifier it renames
that the notation does not mark, such as an identifier in an Examples
cell, and renames those you pick with --write --mentions, so a
rehome no longer leaves stale identifiers behind for a follow-up
amendment. The skill proviso-rehome proposes which to rename and
which to keep.
Fixed
proviso-check no longer misses the amendment itself when a
system-level change splits the check into one run per capability: an
extra run now reads the changed elements against their frames, even
where their capability holds no candidate.