What problem does it solve? Large legacy codebases often have more Plumbline lint violations than a team can fix in one pass, so a strict lint gate would block all work. This Skill records a baseline violation count and fails CI only when a change increases that count, letting teams pay down the backlog incrementally without ever letting it grow. ## Core Features & Use Cases - Baseline Recording: Saves the current violation count and per-check breakdown to .ok-plumbline/budget.json via the save verb. - CI Ratchet Check: The check verb exits 2 only when the count goes up, so PRs that hold or reduce violations pass. - One-Way Enforcement: save refuses to record a higher baseline, making the ratchet strictly monotonic by design. - Use Case: A project inherits 400 Plumbline violations. The team saves 400 as the baseline, and every subsequent PR must keep the count at or below 400; whenever it drops, the new lower number is committed as the new baseline. ## Quick Start Run /ok-plumbline:budget to compare the current violation count against the saved baseline, or run /ok-plumbline:budget save to commit a lower baseline.