Run the applicable static-analysis engines (semgrep security rules, gitleaks secrets, shellcheck, ruff, actionlint) over a change set and return normalized findings. Findings are review LEADS, not verdicts: validate each against current code. Give either base (git ref; scans base...HEAD changed files, secrets over base..HEAD commits) or an explicit files list (repo-relative). A .leveret.yml profile in the repo (or profilePath) scopes engines by path and suppresses priced rules; suppressions come back tallied with their reasons, never silently.

Structural code search via ast-grep: match a syntax-aware pattern (metavariables like $X, $$$ARGS) instead of text. Use for 'every call site shaped like this' questions a text grep gets wrong. Returns file/line/matched text.

Prioritization context for reviewing a change — NOT findings: per-function cyclomatic complexity (lizard, multi-language), 12-month git churn, and last-touched date per file. High complexity in a high-churn file deserves the deepest review; use this to decide where to dig before reading code.

Persist a graded verdict to the repo's review memory (.leveret/memory.jsonl) so the finding class never re-surfaces ungraded. Grades: priced-noise (true but the repo prices fixing it at zero) or false-positive (the claim is wrong). Only drops are stored — actionable findings are reported, not remembered. Give anchorFile + anchorLine to pin an instance verdict to its source line: the memory dies when that line changes. Omit the anchor for a class-wide verdict (fp may use a glob).

List the repo's review-memory entries (fingerprint, grade, reason, created, lastApplied). Use lastApplied to spot dead pricing worth deleting, and repeated same-rule entries under one subtree as candidates for promotion to a glob memory or a .leveret.yml profile rule.