Optional, before writing a general-purpose function or helper your own search didn't find.

Describe what you are about to build in intent (e.g. "retry HTTP calls with exponential backoff"); optionally pass your draft in code. Returns the closest existing symbols, each with a decision: reuse | adapt | write_new; the repo's own helpers for library calls the intent touches (house_helpers); and project conventions. write_new means none of these few matches fits, not that the repo lacks it.

Call when you finish a change, before you report done or commit.

Checks new code for three things. Bloat: duplicates of existing code, dead code, unused imports, redundant checks, single-implementation abstractions, pass-through wrappers, hand-rolled stdlib functions, unneeded dependencies. Error handling: swallowed exceptions, missing timeouts, unchecked subprocesses, unclosed files, imports of project modules or names that don't exist. Security: injection, hard-coded secrets, verify=False, unsafe deserialization, unknown or vulnerable packages. diff is a unified diff; omit it to check the working tree against HEAD. Returns gate=pass|block with findings. Fix blocking findings or reject wrong ones via record_feedback.

Return a smaller version of a Python module with identical behavior.

The rewrite (Nemotron) is pre-checked (Jev) and then run against tests in a sandbox. Tests must import from a module named target. Without tests, tests are generated. A rewrite that changes behavior is rejected and the original is returned.

Run the same tests (importing from module target) against two versions of a module. equivalent is null when there were no tests to run (none given, and none could be generated): unproven, not shown to differ.

Call BEFORE adding a package. Checks it exists on PyPI (catches hallucinated names), known vulnerabilities (OSV.dev), maintenance, and whether something the project already has covers purpose. Returns recommendation: add | use_existing | avoid.

Tell LeanGate whether a finding was right. A rejected finding (accepted=false) is never raised again, except a security finding: only a person can waive one (leangate waive), so tell the user why you think it's wrong instead. If note states a project convention (e.g. "we always validate at API handlers"), it is remembered.

Open LeanGate's live dashboard (127.0.0.1 only) in the browser, showing the latest reports for this repo. Call it only when the user asks to see the report. It starts the local dashboard if it isn't running.