Lint-AI: Skill for Claude Code

Lint-AI Memory

MCP-first memory policy

For requests about project history, prior decisions, architectural choices, earlier work, or "why" something was implemented, the first tool call must be mcp__lint-ai__search. Do not begin with Bash, Read, repository search, or another memory system for those requests.

Use this sequence:

1. Call mcp__lint-ai__search with a concise query describing the missing context.
2. Use the returned results as context and distinguish retrieved facts from current source facts.
3. Check cited files only after the MCP search, and only when the answer also requires current source details.
4. Prefer exact-revision or clearly relevant results and state uncertainty when the results are incomplete.

Use mcp__lint-ai__info only to check MCP workspace status or diagnose the server. It is not a memory search and should not replace search.

Explicit session recording

Session recording is off by default until the user enables Lint-AI. Enabling Lint-AI also starts recording by default. Users can explicitly override this with mcp__lint-ai__record_session and {"action":"stop"}. Recording is capture-only: it records redacted lifecycle events locally and does not inject memory into the session.

When the user asks to stop recording, call the same tool with {"action":"stop"}. Use {"action":"status"} only when the user asks whether recording is active. Never start recording implicitly for ordinary memory searches or project work.

Lint-AI memory controls

When the user explicitly asks to turn Lint-AI memory off, call mcp__lint-ai__disable_lint_ai. When the user asks to turn it back on, call mcp__lint-ai__enable_lint_ai. These controls affect future Lint-AI retrieval and memory capture. Enabling memory also starts recording by default, while disabling memory leaves the recording choice unchanged. Use mcp__lint-ai__lint_ai_status when the user asks whether memory behavior is enabled. Do not toggle memory implicitly during a task.