Call this ONCE at the start of work on a new project, before writing code. Returns the questions to ask the human about their coding standards. Ask them conversationally — do not dump all questions at once. Then call save_conventions with their answers.

Record the coding conventions the human described. Also use this to add or amend rules later. Rules are merged by category+rule text; existing rules are preserved unless replace is true.

Read the project coding conventions. Call this BEFORE writing or changing code, so the change matches the team rules rather than your defaults.

Record an explanation for a change you just made. Call this after every meaningful code edit — before moving on to the next task. The explanation is quality-checked and rejected if it does not genuinely transfer understanding. "I fixed a bug" or "refactored for clarity" will be rejected. You need a session open (call start_session first).

Call this at the very beginning of work on a task. Returns a sessionId to pass to every subsequent explain_change call. If an open session already exists you get it back — no duplicate opens.

Call this when the work is done or the conversation is ending. Writes a human-readable digest to .diffmind/digests/.md that the user can read to catch up on what happened.

List changes recorded in DiffMind, newest first. Use this to orient yourself at the start of a new session, or to answer "what has been done so far?"

Fetch the full explanation for a change by its id. Use this when you need to understand WHY code looks the way it does, before modifying it.

Sends a test notification via the MCP server to verify how Claude Code handles notifications. Used for debugging and testing the notification system.

Mark a knowledge gap as filled when the user demonstrates understanding