// Scan recent changes for AI-generated code slop and remove it. Use when the user says "deslop", "remove slop", "clean up AI code", or asks to remove AI-generated artifacts from the codebase.
Create a GitHub issue from recent changes, commit only relevant diffs on a short-lived task branch, push that branch, and open a PR into master that will close the issue on merge. Use when the user says "make closed issue", "close issue", or wants to create a tracked, already-resolved GitHub issue for completed work.
Commit current work by reviewing diffs, splitting into logical commits, and writing standardized messages. Use when the user says "commit", "commit this", "commit current work", or asks to create a git commit.
Perform a refactor pass focused on simplicity after recent changes. Use when the user asks for a refactor/cleanup pass, simplification, dead-code removal, or says "refactor pass".
Analyze code for useEffect anti-patterns and refactor to simpler alternatives. Use when the user says "you might not need an effect", "check effects", "useEffect audit", or asks to review useEffect usage.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill for X". Use this to search the open skill ecosystem.
Review an open GitHub pull request, inspect feedback from CI, review bots, and human reviewers, decide which findings are valid, implement fixes on the PR branch, merge the PR into master when it is ready, and finalize the linked GitHub issue and project status after merge. Use when the user says "check the PR", "address review comments", "review PR feedback", or "merge this PR".
| name | deslop |
| description | Scan recent changes for AI-generated code slop and remove it. Use when the user says "deslop", "remove slop", "clean up AI code", or asks to remove AI-generated artifacts from the codebase. |
| disable-model-invocation | true |
Scan the diff against main and remove AI-generated slop introduced in this branch.
Get the diff
git diff main...HEAD
If there are also uncommitted changes, include them:
git diff main
Scan each changed file for the slop categories below
Fix each instance — remove or rewrite to match the surrounding code style
Verify the build still passes:
yarn build && yarn test
Report a 1-3 sentence summary of what you changed
AI loves adding comments that restate the code. Remove comments that a human wouldn't write. Keep comments that explain why — domain reasoning, constraints, trade-offs, or non-obvious intent.
// ❌ Slop — restates the code
const [count, setCount] = useState(0); // Initialize count state to 0
// ❌ Slop — obvious from context
// Get the comment from store
const comment = commentsStore.getState().comments[commentCid];
// ✅ Keep — explains non-obvious intent
// pkc-js returns undefined while loading, null if not found
const isLoading = comment === undefined;
AI adds try/catch blocks and null guards everywhere, even on trusted codepaths. Remove guards that the surrounding code doesn't need.
as any castsAI casts to any to bypass type errors instead of fixing the actual types. Remove the cast and fix the underlying type issue.
Any pattern that doesn't match the rest of the file: different naming conventions, different import ordering, unnecessary abstractions, or overly verbose code where the file is concise.
AI tends to add unnecessary abstractions, utility functions, or wrapper layers that obscure simple logic. If a one-liner was wrapped in a helper, unwrap it.
Comments are necessary when code expresses:
When in doubt, check if similar code nearby has comments. Match the file's existing comment density.