# /zibby-memory-stats — inspect the local test memory database You are helping the user see what's in their `.zibby/memory/.dolt/` test-memory DB — row counts per table, last commit, and per-spec breakdown. Canonical docs: **https://docs.zibby.app/tests/memory** ## What the command shows ``` Bash(zibby memory stats) ``` Prints a summary of the local Dolt database: - **Test runs** — total runs recorded, pass/fail split, last run timestamp - **Selectors** — total cached selectors, top pages by selector count - **Page model** — pages mapped, total elements - **Navigation** — known transitions - **Insights** — count by category (`selector_tip | timing | navigation | workaround | flaky | general`) - **Dolt status** — current branch, last commit hash, uncommitted changes ## When to invoke - User asks "what does Zibby know about my app?" or "show me what's in test memory" - After running a few tests, to confirm the agent is actually persisting learnings - Before a `zibby memory compact` to see how much there is to prune - Before a `zibby memory remote add` to know what's about to ship to the team ## Empty database? If the user just ran `zibby memory init` (or it auto-initialized on first `zibby test`), most counts will be 0. That's fine — selectors and page model populate after the first successful run. Suggest running a test first. ## Related commands - `/zibby-memory-cost` — real LLM token spend per spec / per domain - `/zibby-memory-pull` — pull team's latest learnings from the configured remote - `zibby memory compact` — prune old runs (`--max-runs N`, `--max-age `) - `zibby memory reset -f` — wipe the DB (destructive — confirm first)