What problem does it solve? When a project's full-repo detekt run is broken by hundreds of pre-existing violations and no committed baseline, developers cannot tell which violations their own branch introduced. This Skill lints only the Kotlin files changed on the current branch and diffs the SARIF output against the base branch, surfacing only new violations. ## Core Features & Use Cases - SARIF diffing: Runs detekt on changed files in both the current tree and a detached worktree of the base branch, then reports only violations present in the new output. - Safe base comparison: Reads the base branch from a throwaway git worktree instead of stashing or checking out, so uncommitted work and concurrent sessions are unaffected. - Configurable base branch: Accepts a --base flag or auto-resolves the remote HEAD branch, so branches cut from epic integration branches diff against the correct base. - Use Case: Before pushing a Kotlin change in a repo where ./gradlew detekt fails on legacy code, run this Skill to confirm your branch introduces zero new violations. ## Quick Start Ask the AI to lint the Kotlin files changed on the current branch against the base branch and report only newly introduced detekt violations.