Caught, with the
lines that prove it.
Each check reads the files your coding agent’s change writes, and reports what to fix on the lines it touched.
What a check finds
- On the lines it wrote
- A check analyzes the files your agent’s change writes and reports the findings on the lines it added or touched. Findings already in the code are counted, and never fail the check.
- Traced to a rule
- Each finding names the rule that raised it, its severity, its certainty, and the file and line, from Bifrost’s static analysis rather than a language model.
- Never a false all-clear
- A rule that can’t finish makes the check incomplete, never clean, so your agent knows what wasn’t covered.
- In your agent’s loop
- Your coding agent runs slopcop check after each edit and fixes what it finds before you push. It ignores a false positive with slopcop ignore, and later checks leave that finding out.
- On every pull request
- The same check runs on each push to a GitHub pull request, with every new finding on its line in Files changed. See pull request checks.