Agent Skills: review-slop
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.
ID: agenta-ai/agenta/review-slop
4,879724
Install this agent skill to your local
Skill Files
The files that make up review-slop.
Loading file tree…
More agent skills
- sync-findingsSync the findings record against local review artifacts and optionally a GitHub PR. Accept optional `path` and GitHub PR `url`; when `url` is provided, sync against both remote PR state and local state, otherwise default to local-only sync. Default to `path=infer`. Confirm effective variables before starting.
- update-api-docsUpdate the API reference documentation by downloading the latest OpenAPI spec from production and regenerating the Docusaurus API docs
- write-pr-descriptionWrite PR titles and descriptions the way a staff engineer would. Use when drafting or editing a pull request title and body, before running `gh pr create`, or any time the user asks for a PR description, summary, or release-notes-style writeup of a change. Apply this skill from the start, not as a cleanup pass after a generic first draft.
- write-docsUse when writing or editing documentation pages (concept pages, how-to guides, API reference prose, tutorials) under docs/. Provides the writing style, voice, and structural rules for Agenta docs. Apply this skill before drafting any new docs page, and include it in the brief for any subagent tasked with writing docs.
- agenta-package-practicesWhere to put frontend code (package vs the web/mobile app layer) and how to use the @agenta/* packages. Use when authoring or moving code in web/packages, choosing which @agenta/* package owns something (ui, entities, entity-ui, shared, chat, sessions, playground, the *-ui domain packages, ...), using molecules, the loadable bridge, the EntityPicker, or writing package unit tests.
- triage-findingsCoordinate findings work with the user, decide whether scan, test, or sync should run, and turn the current findings set into a ready plan. Accept optional `path` and GitHub PR `url`; default to `path=infer`. Confirm effective variables before starting.