Remove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff. Cleans up boilerplate, simplifies abstractions, strips defensive code, and in skill-file mode lints SKILL.md files for quality. Use when cleaning up code, simplifying, removing boilerplate, before committing, or when reviewing a skill before promoting it.
git clone https://github.com/rohitg00/pro-workflow.git--- name: deslop description: Remove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff. Cleans up boilerplate, simplifies abstractions, strips defensive code, and in skill-file mode lints SKILL.md files for quality. Use when cleaning up code, simplifying, removing boilerplate, before committing, or when reviewing a skill before promoting it. --- # Remove AI Code Slop Check the diff against main and remove AI-generated slop introduced in the branch. ## Trigger Use after completing changes, before committing, or when code feels over-engineered. ## Commands ```bash git fetch origin main git diff origin/main...HEAD --stat git diff origin/main...HEAD ``` ## Workflow 1. Run diff commands to see all changes on the branch. 2. Identify slop patterns from the focus areas below. 3. Apply minimal, focused edits to remove slop. 4. Re-run `git diff origin/main...HEAD` to verify only slop was removed. 5. Run tests or type-check to confirm behaviour unchanged: `npm test -- --changed --passWithNoTests 2>&1 | tail -10` 6. Summarise what was cleaned. ## Focus Areas - Extra comments that state the obvious or are inconsistent with local style - Defensive try/catch blocks that are abnormal for trusted internal code paths - Casts to `any` used only to bypass type issues - Over-engineered abstractions for one-time operations (premature helpers, factories) - Deeply nested code that should be simplified with early returns - Backwards-compatibility hacks (renamed `_vars`, re-exports, `// removed` comments) - Features, refactoring, or "improvements" beyond what was requested - Added docstrings, type annotations, or comments on code that wasn't changed - Error handling for scenarios that can't happen in trusted internal paths ## Guardrails - Keep behavior unchanged unless fixing a clear bug. - Prefer minimal, focused edits over broad rewrites. - Three similar lines of code is better than a premature abstraction. - If you remove something, verify it's truly unused first. - Keep the final summary concise (1-3 sentences). ## Skill-file mode When the target is a `SKILL.md` (not a code diff), lint it against the same slop instinct applied to prose. Run this before promoting a skill. Flag: - **Stale lines** - guidance written for an old version of the skill that no longer matches what it does. Cut it. - **Bloat** - the skill runs past one screen with detail that belongs in a linked reference. Push it down: in-skill step, then in-skill reference, then an external file behind a pointer. - **Dead sentences** - a line that changes nothing if deleted. Delete it. - **Duplication** - the same instruction stated in two places, so edits drift. Keep one source of truth. - **Premature stop** - the method ends before the work does (asks the question but never records the answer, cleans but never verifies). - **Weak anchor** - no single concept the skill turns on. A skill the reader can name in one word triggers and executes in fewer tokens. - **Missing invocation intent** - no declared human-run vs auto-triggered mode. See [`rules/skill-conventions.mdc`](../../rules/skill-conventions.mdc). - **Wrong write op** - a state-changing skill that does not say whether it adds, updates, or appends, or that duplicates its output on a second run. **Skill-file mode output:** the flagged issues by line, the edits applied, the cleanup summary, and whether the skill is ready to promote. ## Output (code mode) - List of slop patterns found with file locations - Edits applied - One-line summary of what was cleaned
[{"step":"Identify the branch or files to clean up. Use `git diff [BRANCH_NAME]` or `git diff --name-only` to preview changes.","tip":"Run `git status` first to confirm you’re on the correct branch."},{"step":"Run the deslop skill with a focused area (e.g., `[FOCUS_AREAS]='boilerplate,defensive-code'`). For SKILL.md files, use `[FOCUS_AREAS]='lint,clarity'`.","tip":"Use `git diff` to pipe changes into the prompt if working with large diffs: `git diff | pbcopy` (Mac) or `git diff | xclip` (Linux)."},{"step":"Review the cleaned diff output. Manually verify critical logic (e.g., error handling) wasn’t removed accidentally.","tip":"Focus on preserving business logic and edge cases. Use `git diff --cached` to compare against staged changes."},{"step":"Apply the cleaned changes by copying the diff into a new commit. Use `git commit -m 'Clean up AI slop and over-engineering'` or `git apply` for file-specific changes.","tip":"Use `git add -p` to selectively stage changes if unsure about some parts."},{"step":"For SKILL.md files, ensure the linted version is committed and pushed. Check for readability and alignment with your project’s documentation standards.","tip":"Use tools like `markdownlint` to validate the final SKILL.md file."}]
No install command available. Check the GitHub repository for manual installation instructions.
git clone https://github.com/rohitg00/pro-workflow/tree/main/skills/deslopCopy the install command above and run it in your terminal.
Launch Claude Code, Cursor, or your preferred AI coding agent.
Use the prompt template or examples below to test the skill.
Adapt the skill to your specific use case and workflow.
Clean up the current branch diff by removing AI-generated code slop, unnecessary comments, and over-engineering. Focus on: [FOCUS_AREAS]. For each file changed, simplify abstractions, strip defensive code where safe, and remove boilerplate. If in SKILL.md mode, lint the file for quality, ensuring clarity and conciseness. Output the cleaned diff in a unified format. Current branch: [BRANCH_NAME].
Here’s the cleaned diff for the `feature/auth-optimization` branch after removing AI slop and over-engineering:
```diff
--- a/src/auth/middleware.ts
+++ b/src/auth/middleware.ts
@@ -1,25 +1,12 @@
-// Middleware to validate JWT tokens with advanced error handling
-// Supports multiple token formats and includes rate limiting
-export const validateToken = async (req, res, next) => {
- try {
- // Extract token from Authorization header
- const authHeader = req.headers['authorization'];
- if (!authHeader) {
- return res.status(401).json({ error: 'Authorization header missing' });
- }
-
- const token = authHeader.split(' ')[1];
- if (!token) {
- return res.status(401).json({ error: 'Bearer token missing' });
- }
-
- // Verify token using JWT library
- const decoded = await jwt.verify(token, process.env.JWT_SECRET);
- req.user = decoded;
- next();
- } catch (error) {
- // Handle all possible JWT errors with detailed messages
- res.status(403).json({ error: error.message });
- }
-};
+export const validateToken = async (req, res, next) => {
+ const authHeader = req.headers['authorization'];
+ if (!authHeader) return res.status(401).send('Unauthorized');
+
+ const token = authHeader.split(' ')[1];
+ if (!token) return res.status(401).send('Unauthorized');
+
+ req.user = await jwt.verify(token, process.env.JWT_SECRET);
+ next();
+};
```
Changes made:
1. Removed redundant error handling (AI slop) that overcomplicated the flow.
2. Simplified the token extraction logic (no defensive checks for 'Bearer').
3. Removed unnecessary comments explaining obvious code.
4. Inlined the JWT verification result directly into the middleware.
SKILL.md linting (if applicable):
- Removed redundant sections like 'Prerequisites' that were auto-generated.
- Simplified the 'Installation' steps to a single command.
- Removed AI-generated placeholder text like 'TODO: Add more details'.skills-collection
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan