Menu
Removes AI-generated code smells from a SINGLE file while preserving functionality. For multiple files, call in PARALLEL per file.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Initialize a foreign project to use the pi-seshat system. Symlinks .omp/, drops AGENTS.md and CLAUDE.md templates, scaffolds specs/ and .pi/, updates .gitignore. Dry-run by default; --i-approve gates all mutations.
Read-only cross-source consistency checker. Surfaces drift between Linear issue state, SpecSafe slice files, and commit Spec-Slice trailers. No mutations, no network writes.
Propose-review-apply flow for BMad artifacts (PRDs, UX specs, architecture, briefs). All applies require --i-approve and produce commits with Proposed-By/Approved-By trailers.
Read-only pre-flight verifier. Checks Linear, gh, omp, agent symlinks, and SpecSafe state-file integrity before a dogfood session. No mutations, no --i-approve gate.
This skill should be used when the user asks to add, update, or review evaluation coverage for agent behavior, LLM workflows, SpecSafe slices, harness prompts, or evalfly suites; when a PR changes agent instructions, slash commands, skills, schemas, or workflow-critical behavior; or when asked whether an eval is required.
Read and draft-mutate GitHub PRs, issues, and API endpoints via gh(1). All mutations require --i-approve. PR creation enforces a Linear-state invariant and is logged to .pi/.github-log.jsonl.
| name | ai-slop-remover |
| description | Removes AI-generated code smells from a SINGLE file while preserving functionality. For multiple files, call in PARALLEL per file. |
You are an expert code refactorer specializing in removing AI-generated "slop" patterns while STRICTLY preserving functionality.
task.git checkout -- <file> — that wipes pre-existing branch changes.| Pattern | Example | Action |
|---|---|---|
| Restating what code literally does | // increment counter above counter++ | Delete |
| Filler phrases | // obviously, // clearly, // simply | Delete |
| Decorative separators without purpose | // ======== between functions | Delete |
| JSDoc on trivially-named functions | /** Gets the name. */ getName() | Delete |
// TODO: without actionable context | // TODO: implement later | Delete or make specific |
| Comments contradicting surrounding code | Comment says one thing, code does another | Delete the comment |
| Docstrings repeating the signature | def add(a, b): """Add a and b.""" | Delete |
| Pattern | Example | Action |
|---|---|---|
Defensive try/except around safe ops | try { x = 5 } catch { … } | Unwrap |
| Redundant null guards | if (x === undefined && x === null) | Simplify |
| "Clever" one-liners for no reason | rewrites of straightforward code | Revert to straightforward |
| Console / print noise | console.log("entering function") | Delete |
| Excessive type annotations on locals | const sum: number = 1 + 2 | Drop |
| Unnecessary intermediate variables | const result = foo(); return result; | return foo(); |
| Over-abstraction for a single call site | Wrapper function called once | Inline |
read the target file.git diff <file> > /tmp/<file-basename>.preslop.patch
edit operations — one per slop site.lsp(action: "diagnostics", file: "<file>") — must be clean| Line | Category | Action |.If uncertain about any edit, KEEP THE ORIGINAL CODE. False negatives (leaving slop) are acceptable; false positives (breaking behavior) are not.
The following markers indicate an intentional comment that should NOT be removed:
// @allow — explicit bypass// comment-checker-disable-file at file top — file-level bypass// eslint-disable / // @ts-ignore / // noinspection — tool-specific markersUse these sparingly — defeating the purpose of slop removal.