context-health

To audit personal assistant context files for staleness and bloat, run a context-health scan that performs timestamp checks, counts lines and empty sections, and cross-references rules to flag outdated or bloated entries. The scan generates a summary table with prioritized cleanup actions.

Generic responses often happen when context files contain bloat, contradictions, or out-of-sync aggregated rules. A context-health audit detects these issues by counting lines, verifying cross-file sync, and checking for empty guide sections, then recommends cleanup to restore specific, accurate responses.

You should run a context audit periodically, after major life changes, or before planning sessions. The audit checks timestamp staleness across triggers, sessions, and projects, and verifies system freshness including model-capability recency, ensuring your assistant's memory remains accurate and relevant.

Yes, you can check for contradictions and missing data by running a context-health audit that compares preferences, rules, identity, and workflows. It performs cross-file sync verification and gap analysis to surface conflicts and missing profile or workflow sections.

The best way to clean up stale triggers and forgotten session entries is to use an automated context audit that performs timestamp inspections across your local context files. It identifies old entries and produces a prioritized tabular summary for targeted remediation.