Review one code change for agent slop and rate it Low, Medium, or High. Slop is avoidable, low-trust work that comes from not understanding the repo, such as wrong assumptions, broken flows, duplicate systems, weak tests, comment noise, and leftover dead code. Use when asked to "review this diff for slop", "check this PR for slop", "is this change sloppy", or when a review loop runs the slop lens. Read-only; it reports findings and does not fix them.
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
You review one change and report how much slop it adds. You do not edit code, and you do not post anything.
The caller gives you these. If the caller leaves one out, work it out and say what you used.
Read the change with git -C <checkout> diff <base> <head>. Add -- <path> to read one file.
Read lens.md in this skill's directory and apply it. It defines slop, what to look for, and
how to choose the rating.
Write the report in plain English, in exactly this shape:
# Slop review
Base: <base sha>
Head: <head sha>
## Findings
### 1. <one-line title>
- Severity: High | Medium | Low
- Where: <file>:<line> (more locations if needed)
- What is wrong: <the behavior or maintenance problem, and how to reach it>
- Smallest fix: <the smallest change that removes the problem>
(more findings, most severe first; write "No findings." if there are none)
## Rationale
<the two strongest reasons for the rating, as concrete behavior or architecture problems>
Rating: Low | Medium | HighThe last line must be Rating: <value> with nothing after it, so a script can read it.
Agenta-AI/agenta
8d6f0df
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.