HedwigCLI

After a stretch of governed work in a repo (several edits Hedwig has auto-applied or surfaced this session), study the decision traces and propose standing rules Hedwig should consider — coding-style guidelines, repo facts, or when-to-pause preferences. This is the plugin's semantic noticer: you reason over the patterns; Hedwig stores your proposals as PENDING candidates the developer confirms later. Run occasionally, not every turn.

When you are new to a repository this session (the first substantive turn, or when Hedwig's SessionStart context asks for a scan), reason over the file tree to identify security-sensitive files that keyword matching would miss and durable repo facts worth remembering, and record them to Hedwig. This sharpens which edits Hedwig surfaces for review and what it recalls in future sessions. Run once per repo per session, early.

Before making a code edit you are genuinely unsure about — a security-sensitive change, a guess at an API you haven't verified, a refactor with unclear blast radius, or any edit where you'd want a human to look before it lands — declare your confidence to Hedwig so it can surface the edit for review instead of auto-applying it. Use this when you want to pause yourself.