Dev10x:context-audit

To optimize context window usage, you can audit your environment by scanning files against documented budgets to identify bloat and receive specific context pruning suggestions for oversized files.

Context pruning is the process of removing redundant or oversized data from the context window. You need it when sessions feel sluggish or after adding many rules and memories that cause context bloat.

You audit context utilization by scanning files and checking them against documented budgets, which flags oversized files and identifies redundancy to ensure efficient memory management.

Yes, the context audit supports various tools including Bash scripts, Grep, Glob, Read, and AskUserQuestion to scan files and check against documented budgets within the Claude environment.

The best way to manage AI context bloat is to run a structural context audit that reviews all context sources for compliance with budgets and suggests targeted pruning actions for excess memory.

Your session feels sluggish due to context bloat from oversized files and redundant memory rules, which an audit can identify by scanning against documented budgets and suggesting pruning actions.