← ClaudeAtlas

lintro-reviewlisted

AI branch review using lintro's own `lintro review` — a standard local pre-push pass alongside the coderabbit and greptile CLIs, and the review of record when those are rate-limited or unavailable. Use when asked for a lintro review, an interim/fallback AI review, or as part of the default pre-push review set.
lgtm-hq/ai-skills · ★ 0 · Code & Development · score 66
Install: claude install-skill lgtm-hq/ai-skills
# Lintro AI Review (standard local pass) Run **lintro's own** AI diff review (`lintro review`) on the branch. Since 2026-08-02 (owner instruction) this is a **standard third local pre-push pass** alongside `coderabbit` and `greptile`, not just a fallback — and when those two are rate-limited or down, the lintro pass is the AI review of record for the push. ## When to use - As part of the default pre-push review set (`coderabbit` + `greptile` + this). - CodeRabbit and/or Greptile are rate-limited, erroring, or otherwise unavailable. - You want an AI pass on the branch diff (or working tree) right now. At **final merge**, bot threads that did get posted on the PR must still be triaged; a local lintro pass doesn't resolve GitHub threads. ## Two correctness rules (do not skip) 1. **Use released lintro via `uvx`, never `uv run lintro`.** The reviewer engine must be stable and independent of the working tree — especially when the branch is itself modifying lintro's AI/provider layer (you must not review half-migrated code with itself). Floor is **`>=0.94.7`**: that release carries both the CLI auth-mode detection (#1859, subscription OAuth works) and the CLI stdout error surfacing (#1836). 2. **Enable AI locally behind a `skip-worktree` guard.** Many repos (incl. py-lintro) ship `.lintro-config.yaml` with no `ai:` block or `ai.enabled: false`. Flip it on locally in a way that cannot be staged or committed. ## Steps 1. **Enable AI locally without commit