What problem does it solve? A Qlty check fails with "Build errored. Check the log for more information." and the cloud build log shows linter stderr instead of findings — typically an ESLint version banner followed by a TypeError like "contextOrFilename.getFilename is not a function". This happens because Qlty installs its own ESLint runtime, which may be a major version incompatible with the locked eslint-plugin packages, crashing the linter at rule-load time. ## Core Features & Use Cases - Crash vs. outage diagnosis: Distinguishes a runtime crash from a transient Qlty cloud outage by reading the cloud build log, avoiding useless retries. - Runtime pinning: Adds a version field to the [[plugin]] name = "eslint" block in .qlty/qlty.toml, matched to the version resolved in the repository's lockfile. - Second-order fix: Replaces settings.react.version: 'detect' with a literal React major.minor in eslint.config.mjs so eslint-plugin-react no longer calls the removed context.getFilename() API. - Use Case: After bumping ESLint or copying a .qlty/qlty.toml pin from a sibling repository, a pull request's Qlty status goes red with zero findings; this Skill reads the build log, pins the runtime to the lockfile's resolved version, and verifies the fix against the repository's lint gate. ## Quick Start Diagnose why my Qlty check is red with a build error and fix the ESLint runtime version pin in .qlty/qlty.toml to match my lockfile.
