Docs menu
Get started
Quickstart Install: Claude Code Install: Codex Install: other clients API keysConcepts
How a run works The app profile The severity model What a run does not sayTools
check_access claim_trial_key set_profile run_lint get_law resolve_domain_jurisdiction submit_feedback upload_lint_runGuides
A whole run, end to end Console TestPack in CIReference
Endpoint and transport lexlint.yml schema Errors ChangelogHelp
Support and feedbackHelp
Support and feedback
Tell the people who build LexLint what went wrong, from the session where it went wrong.
From your session
Run /lexlint-feedback in Claude Code, or have any agent call the
submit_feedback tool.
It writes your feedback on LexLint to the people who build it, recorded against your UnGovr account so we can write back.
The submit_feedback page lists what the tool takes, and what an agent should show you before it sends anything.
On GitHub
Open an issue on the public plugin repository, where the plugin's commands, skills and schema are kept: https://github.com/ungovr/lexlint/issues
Questions about LexLint
The FAQ answers what LexLint covers, what it costs and what it sees of your code: https://lexlint.io/faq