Yapermission

Dry-run a tool call against the active yapermission policy and report which rule matched and why. Trigger when the user asks to test/debug/trace a yapermission rule, check whether a command would be auto-approved or blocked, or understand why a yapermission decision happened.

Scaffold the global yapermission config at ~/.yapermission.toml from a bundled template. Two templates are offered — `starter` (default-ask, conservative) and `yolo` (default-allow with hard guardrails). Trigger when the user asks to set up yapermission, initialize the policy file, or create a starter/yolo yapermission config.

Cache an approved `[[ask]]` decision for the rest of the current session so the same rule matching the same exact tool call stops re-prompting. Trigger only after the human has explicitly said yes to an offer to remember a yapermission decision — never on your own initiative, never on an assumption that they would want it.

Reference for the yapermission TOML rule schema and evaluation order. Trigger when the user asks how to write a yapermission rule, the yapermission toml format or schema, how to auto-allow git commands or shell utilities, how to force a prompt for force-push or other commands, how to block rm -rf or other dangerous commands, or how project and global yapermission configs interact.