li-analyze

Use when a workflow explicitly hands work across a boundary — spawning a subagent, transitioning a phase, passing to a cold executor, or taking operator input…

Use for data-architecture depth — schema design, migrations, sharding and partitioning, query-pattern audits, retention policy, and analytics readiness.

Use when a non-trivial decision needs recording to bootstrap a new Architecture Decision Record from the template, asking context-gathering questions to fill…

Use when evaluating declared controls with mandatory, advisory, unverified and no-applicable outcomes; this is not host enforcement.

Use to add, list or lift advisory session freeze paths; preserves project policy and never grants or removes host write permission.

Use before landing a change to review just the diff — focused on the changed code only, lighter than a full engineering review.

Use to load bounded files, topic-related sources, ADRs or prior sessions with safe selection and honest input-size estimates before reading.

Load customer-engagement repo state into context — their infrastructure-as-code, their CLAUDE.md, their ADRs, recent commits.

Retrieve bounded external reference text only through explicit host policy and redirect checks, preserving source provenance and trust boundaries.

Use before a large read or handoff, or when context headroom and resource advice are needed; keep observed usage, source estimates and unknown limits distinct.

Use to identify the current CLI, desktop, IDE or cloud surface and inspect its actual tools without inferring capability from a vendor name.

Exclude explicitly selected files from future context reads without claiming to remove already-sent conversation content.