# Integrations Bring the same static checks to the places you write and review agent instructions. Choose a CI gate, a local commit hook, or feedback inside your coding agent. ## CI & code review

GitHub Actions

Check pull requests and publish SARIF findings to Code Scanning.

Setup guide →

GitLab Code Quality

Bring findings and source locations into merge request reviews.

Setup guide →

pre-commit

Check changed instruction files before they enter your repository.

Setup guide →
## Inside your agent

Claude Code

Audit a named file or receive guidance after supported edits.

Setup guide →

Cursor

Ask the lintlang-audit skill to review the file you are working on.

Setup guide →

GitHub Copilot CLI

Review instructions and tool definitions with an on-demand skill.

Setup guide →

Pi

Add a portable skill that runs your installed scanner on named files.

Setup guide →

Gemini CLI

Receive repair guidance after successful write_file and replace calls.

Setup guide →

OpenCode

Add post-edit feedback through the documented legacy adapter.

Setup guide →

Hermes Agent

Check eligible changed files at the first verification attempt.

Setup guide →
## Your linting stack

MegaLinter

Add AI_LINTLANG to your existing MegaLinter checks.

Setup guide →
## Choose how findings affect your workflow CI and commit hooks can enforce an explicit severity threshold. Native audit skills and post-edit hooks give you findings to review in the host; Hermes Agent can request one verification continuation. Each setup guide explains its trigger, verification steps, and recorded host version where applicable. You can also scan host instruction files directly with the [CLI](/docs/cli), without installing a host integration. Start with the [quickstart](/docs/quickstart), then use [baselines](/docs/baselines) to adopt a gate around an existing backlog. ## Public ecosystem references
Browse public usage and ecosystem sources These are observations of public artifacts, checked on 18 September 2026. Usage, packaging, and catalog entries are different kinds of evidence. None is an endorsement, an accuracy measurement, or a claim of broad production adoption. Historical third-party pins are evidence of those artifacts, not installation recommendations for the current package. | Public source | Observed evidence | Boundary | | --- | --- | --- | | Character.AI Larch [CI requirements](https://github.com/character-ai/larch/blob/ef7ee4b7f946f29fa51981f5422a1a93e83c79a7/.github/workflows/requirements-agent-linters.txt) and [linting reference](https://github.com/character-ai/larch/blob/210d08a8f6c1b0dd14c27b709c66471bd31a5636/docs/linting.md) | Pins `lintlang==0.3.1`; documents recurring agent-instruction CI with a HIGH/CRITICAL gate | Public repository usage, not an organization-wide deployment claim | | MegaLinter [plugin catalog](https://github.com/oxsecurity/megalinter/blob/baf2c7a3432b670096a293dc7512848b5e5db349/docs/plugins.md) | Lists the LintLang external plugin as `AI_LINTLANG` | Catalog inclusion, not a built-in default or endorsement | | [Awesome Gemini CLI](https://github.com/Piebald-AI/awesome-gemini-cli/blob/19ee73879458321ea19803d5349bc1341a972eff/README.md) | Lists LintLang and its Gemini CLI extension | Discovery listing, not additional host verification | | [Best of Python Dev](https://github.com/ml-tooling/best-of-python-dev/blob/71e4fe7dbc62d3f6fa2ed5ef7f43245fb5f15349/projects.yaml) | Includes LintLang in its linter catalog | Catalog record, not evidence of detector quality | | [Awesome Hermes Skills](https://github.com/ZeroPointRepo/awesome-hermes-skills/blob/786e092c02e428a09aff61b0381fc11395b7e0a0/README.md) | Includes a LintLang reference | Community listing, separate from the native hook contract above | | [Haven overlay metadata](https://github.com/thehaven/haven-overlay/blob/d052d950b05389fcd7c8f22939033319a5aec348/dev-util/lintlang/metadata.xml) | Package metadata names this repository as upstream | An unofficial Gentoo overlay, not official Gentoo distribution support | Research provenance is a separate question; see [Research and design lineage](/docs/research). For detector behavior and machine-readable contracts, use the [technical reference](/docs/reference). Return to the [README](/docs) for product scope and the main documentation index.